Select to view content in your preferred language

Survey123 Report Generation Down Nov 14th 2025

463
6
3 weeks ago
CherylWheeler11
Regular Contributor

Is anybody else having issues with generating reports in Survey123 today?

We get the below failure on all our attempts at reports from various feature services and surveys.

0 Kudos
6 Replies
CBarrett
Occasional Contributor

Yes I also got this error overnight with no changes to my survey, services, or report template. I went through and removed all the layers it said had problems drawing (which were not critical for my report luckily) and it succeeded again.

I attempted to open a support ticket about this but haven't heard back from support.

0 Kudos
Derrick_Westoby
Occasional Contributor

Wasn't there a S123 update early last week or the week before?  

I have 2x surveys that use Power automate to generate and email reports automatically.  Something happened with the webhook on one of the surveys and I had to set up a new one to fix report generation.  

On the other survey, some submissions are triggering the webhook and others are not, but ALL reports are failing to generate.   

0 Kudos
Derrick_Westoby
Occasional Contributor

Cross-posting here, for those that are also having Power Automate issues after the most recent update:

Re: Survey123 Connection to Power Automate Issues - Esri Community

0 Kudos
ALCOSANGIS
New Contributor

We experienced this same failure mode, Power Automate 'Create Report' action fails with the following error. *This was also observed directly from the Survey123 website when attempting to manually create a report.

        "status""printFailed",
        "messages": ["An error occurred when rendering by the report engine.  Failed to print map for `${point_loc | map:\" guid\" | mapScale:xyzxy| size:xyz:0}`.  The layer \"layerName\" did not draw completely."

I believe this is the result of a change to the S123 report engine no longer allowing maps containing data with multiple coordinate systems. Once all data sources not in WGS84 Web Mercator were removed from the called map the report engine functioned as expected. This was not called out in the survey123 website update notes from 11/13 but I believe that is the change that caused this failure since nothing else was changed in that process since the last successful run.

I have not experimented with other coordinate systems to see if the current version of the report engine is requiring WGS84 web mercator, or if it only requires all data sources to use the same coordinate system.
0 Kudos
CherylWheeler11
Regular Contributor

An update from our side.....it appears that the latest S123 update has meant that layers with visibility turned off in the map used for the report cause the report generation to fail. Once these 'invisible' layers were removed from the map, the report succeeded.

0 Kudos
ZhifangWang
Esri Regular Contributor

Hi everyone,

Thank you for the feedback. We've identified an issue that if there is any invisible layer in the web map, printing a report using the web app will trigger the error "The layer <layerName> did not draw completely". This was introduced in the Survey123 November 2025 update on 11/13.

We have applied a fix to the Survey123 website earlier today. Please let us know if you still encounter this error.

0 Kudos