Survey123 Report Fails when Map element included

Question

I have been having issues with Survey123's report templates for the past month or so.

Reports that don't include a map element work OK, but if a map element is included then the report times out and fails to generate. My reports that included map elements had previously been working fine.

In our live environment Survey123 is configured on ArcGIS Enterprise with survey data coming from internal SDE. Initially I'd thought the issue was perhaps to do with our environment or the version of Survey123 Connect used to publish the survey.  But I have since did some more testing on AGOL and am experiencing the same issues (published survey using Survey123 Connect v3.18 and survey layer hosted on AGOL).

The post at https://community.esri.com/t5/arcgis-survey123-questions/report-fails-with-error-connection-timed-out/m-p/1276712 also describes what typically happens, whenever the map element is included.

ESRI Support suggested including the 'drawinginfo' method along with the feature service URL.. in my case

${Location | drawingInfo:" https://services1.arcgis.com/i8LHQZrSk9zIffRU/arcgis/rest/services/service_f976dee86f22460da0f74cecbe7d2433/FeatureServer/0"

but this also fails to generate the report.. Error message below

An error occurred when rendering by the report engine. Failed to print map for ${Location | drawingInfo:" https://services1.arcgis.com/i8LHQZrSk9zIffRU/arcgis/rest/services/service_f976dee86f22460da0f74cecbe7d2433/FeatureServer/0"}. Runtime.callFunctionOn timed out. Is anyone else experiencing problems like this?Grateful for any feedback.

SusanPollard · Answer

also having this issue. Report map times out for some users when zoomed out to 5km buffer but loads results and logo. Works intermittently for some. Any solutions?

cat206 · Answer

I'm getting the same error too, has either of you found a solution?

MichaelKohn_PGE · Answer

Good Morning, I've been trying to run feature reports that contains a web map and am getting the same error. After attempting to change the item id to a different map the same error still occurs.

I used this syntax: ${$shape | map:”50c20892fa174712871e802765a97cb1”:1000}

The error message is this:

An error occurred when rendering by the report engine. Failed to print map for ${$shape | map:”50c20892fa174712871e802765a97cb1”:1000}. Runtime.callFunctionOn timed out.

This is similar syntax that I use in other feature reports templates that pull maps and it works there.

Is there a Feature Report bug that is preventing maps to print on reports?