# Delays on ingested imagery uploaded from 11th Oct **URL:** \ **Category:** Contributing and equipment\ **Created:** [October 12, 2025, 1:19pm UTC](https://forum.mapillary.com/t/delays-on-ingested-imagery-uploaded-from-11th-oct/10021 "2025-10-12T13:19:31Z")\ **Posts on this page:** 1\ **Showing post:** 23
**Author:** ![GITNE](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/gitne/32/70659_2.png) [@GITNE](https://forum.mapillary.com/u/GITNE)\ **Post date:** [December 6, 2025, 11:45am UTC](https://forum.mapillary.com/t/delays-on-ingested-imagery-uploaded-from-11th-oct/10021/23 "2025-12-06T11:45:22Z")
> [@osmplus\_org](#): > > I’ve been reviewing my upload history and noticed that videos with more than 2800 GPX points are apparently not being processed by Mapillary and therefore remain yellow in the timeline. Sequence image count has very little to do with the chance a sequence getting stuck in processing, despite it being a reasonable but naive assumption from a contributors point of view. It is a function of image density per area and load on the indexing service. > [@WebApp AI Fetch Issue - Looking for help](https://forum.mapillary.com/t/webapp-ai-fetch-issue-looking-for-help/9973/15): > > Our current indexing solution is based on S2 cells and the increased latency correlates with how densely given area is covered with images. For example querying a 1km x 1km bbox in an area with 500 images will be faster than one with 5000. > [@Consistent HTTP 500 Errors on Graph API (/images and /map\_features) Endpoints Since Nov 7](https://forum.mapillary.com/t/consistent-http-500-errors-on-graph-api-images-and-map-features-endpoints-since-nov-7/10077/3): > > Albeit a bit cryptic, this error indicates a generic timeout. Likely there was too much data in the given bbox and serving it is causing a timeout. Very densely captured areas might timeout sometimes despite relatively small bounding boxes. Apparently, 3D reconstruction (the “Map Data Processing” stage) is built on the same query mechanism as the public facing Mapillary API or its query mechanism is prone to the same limitations. Hence, if an area is too densely populated with images for a given query area and the indexing service is under too much load then 3D reconstruction queries just timeout and reconstruction seizes. Ergo, a sequence gets stuck in processing. 🤷 However, there is hope for improvement on the way: > [@Consistent HTTP 500 Errors on Graph API (/images and /map\_features) Endpoints Since Nov 7](https://forum.mapillary.com/t/consistent-http-500-errors-on-graph-api-images-and-map-features-endpoints-since-nov-7/10077/5): > > We did change underlying spatial indexing services in October. I’ll investigate if something change in other components that we depend on around the beginning of November. Appreciate all the reports! --- _[View the full topic](https://forum.mapillary.com/t/delays-on-ingested-imagery-uploaded-from-11th-oct/10021)._