A feature report that has been running without issue for years now times out when map settings are applied. I can run a report with a generic map and even when applying a size restraint. Will timeout when trying to use a specific map ID.
Does not work:
${closure_area|mapSettings:"8f3845a647d04d3c92f10be0299fa2b3": 3600 | size:600:500}
Will work:
${closure_area| size:600:500}
Hi @JustinConnerWR ,
We confirmed that a bug was introduced with the Survey123 July 2025 Update: printing a report that contains a map will time out if the map includes the same feature layer specified in the featureLayerUrl parameter to the report API. For example:. For example:
This was reported as BUG-000177676 and will be fixed in a hotfix early next week.
Could you confirm if this matches your workflow, or are you seeing a different scenario?
I'm having this issue as well. Geotrace questions fail on the report, even when no map is specified. Geopoint questions will work with no map specified.
I've tried re-creating the survey in a new layer, I cannot get a geotrace layer to print to report at all.
Hi @JustinConnerWR @MCostley ,
The fix to BUG-000177676 has been deployed to the Survey123 website earlier today.
Please let us know if you still observe any issues when printing a report with a map.
Thanks,
Zhifang
All good on my end, thank you!
Was working flawlessly this morning, now I'm having the same issues as this thread: https://community.esri.com/t5/arcgis-survey123-questions/survey123-report-generation-down/m-p/163125...
The odd report will go through, but taking over 10 minutes and several tries to do so.
I suspect they were working on it at that time. Ours worked in the morning, was intermittent during midday, and have worked since about 3 yesterday. I am curious if you noticed if you Basemap Selection was empty during this problem? Mine is working again this afternoon, but it had been blank since the issues started.
Yep, up again for me too. Must have just been down at the time I needed it.
I use Google Satellite for that report and had no issues with the display.