topic ECONNRESET in ArcGIS Survey123 Questions

ECONNRESET

ANRGIS — Thu, 18 Jun 2026 15:46:07 GMT

We are seeing the ECONNRESET issue persistently on some survey reports we have published... The error is:

An error occurred when querying data from the feature layer. request to https://services5.arcgis.com/Uzks6LSde6r23wwG/arcgis/rest/services/service_<serviceID/Query/Layer>. failed, reason: read ECONNRESET

Recently we've been seeing serious instability when generating reports on submitted surveys. Whether it be on survey123.arcgis.com or through our Power Automate ArcGIS Connector. It seems like for some surveys, it takes a few tries before the report is generated. This has been causing significant issues for our surveying community. We've also seen an unrelated issue associated with check boxes not working in our PDFs. It was reported by @Ruth_JiatengXu that this was due to a "recent security update for the Report feature" in this thread: https://community.esri.com/t5/arcgis-survey123-questions/s123-pdf-reports-with-no-checkboxes/m-p/1708659#M66420

Could these issues be related?

Re: ECONNRESET

ANRGIS — Thu, 18 Jun 2026 16:44:33 GMT

Even though the report finishes successfully, if you look at the raw output, it shows a failure:

{

"statusCode": 200,

"headers": {

"ETag": "W/\"4e2-6R34h/AwilzxBiPzwGpn5vzv0XM\"",

"Vary": "Origin,Accept-Encoding,Authorization,X-Esri-Authorization",

"arcgis_connector_version": "ArcGIS 2026.2.0 2026.05.13 1778680964496 45012c",

"X-Powered-By": "Express",

"x-ms-environment-id": "default-20b4933b-baad-433c-9c02-70edcc7559c6",

"x-ms-tenant-id": "20b4933b-baad-433c-9c02-70edcc7559c6",

"x-ms-dlp-re": "-|-",

"x-ms-dlp-gu": "-|-",

"x-ms-dlp-ef": "-|-/-|-|-|-",

"x-ms-mip-sl": "-|-|-|-",

"x-ms-au-creator-id": "7d3cd2c3-b152-4636-8118-2dd431bd390b",

"Timing-Allow-Origin": "*",

"x-ms-apihub-cached-response": "true",

"x-ms-apihub-obo": "false",

"Date": "Thu, 18 Jun 2026 16:14:25 GMT",

"Content-Length": "1250",

"Content-Type": "application/json; charset=utf-8"

"body": {

"jobId": "fff47b8f7dd74683afc86f003c9c2528",

"jobStatus": "esriJobFailed",

"jobStatusInfo": {

"detailedStatus": "prepareFailed",

"startTime": 1781799251033,

"progress": 0

"submitted": 1781799250864,

"completed": 1781799264444,

"resultInfo": {

"title": "FWDSiteVisitReport"

"inputInfo": {

"jobType": "createReport",

"parameters": {

"featureLayerUrl": "https://services5.arcgis.com/<orgID>/arcgis/rest/services/service_<ServiceID>/FeatureServer/0",

"queryParameters": {

"objectIds": "695"

"templateItemId": "<templateID>",

"surveyItemId": "<itemID>",

"portalUrl": "https://www.arcgis.com",

"outputFormat": "pdf",

"outputFileName": "FWDSiteVisitReport"

}

"messages": [

"An error occurred when querying data from the feature layer. request to https://services5.arcgis.com/<orgID>/arcgis/rest/services/service_<serviceID>/FeatureServer/1?f=json&token=almDQnmPugMjmZy0rs4ypKQ..anHPBFp4DBk0f7qUGSkeVIb7DerHBhU0PL9tuhnriN1WioYjXHoyEhcnupoKXRuMpylVhew62bTo8PhZHV6vJv_TSnlXyyT3sLmbi1ps6rUmA7VSXpawEbEfU1XLc5uoWx5KuZ1juM4IuW51SqHQIBHGsE3qPH3nBmMDf3WUCPvUWROs4HEttDfVY2t84_dnq1T-mUGuj4cppWzzCUWUIzqwfEfiVondqvf8z4gISE3xGTN3iM0LXtzPTN0NxCWj34NI4nv8-Q-2L9Q3Q_8. failed, reason: read ECONNRESET"

]

}

Re: ECONNRESET

RalphPlummer — Thu, 18 Jun 2026 17:51:36 GMT

I want to comment on this so it is known that @ANRGIS is not the only one seeing this issue. My organization just submitted a ticket regarding this. As reported here, it is hit or miss. My workflows are setup to keep trying every minute for 10 minutes. Most are going through after several tries, some go through 10 tries and fails completely. Manually generating provides the same results. Something fishy is going on. Hopefully we get to the bottom of it.

Re: ECONNRESET

amyb27 — Thu, 18 Jun 2026 19:41:22 GMT

Hi @ANRGIS,

It does look like the internal team found that this issue is no longer reproducible as of a few hours ago. Could you confirm if you are still coming across this error, or if it now works as expected?

Re: ECONNRESET

ANRGIS — Fri, 19 Jun 2026 17:06:50 GMT

After running several sample reports, it does appear to be working more consistently. I will report to our field teams and will resume reporting operations. Thank you for looking into this for us!