I am trying to create a report for a survey that has approximately 40 records.
When I try to create a sample template in manage templates, I receive an error message that states, “An error occurred while saving the report template” The error code is 504.
I was able to create a sample report template in two other surveys, so the issue is with this survey.
A web search for the error code has been less than helpful.
If you have run across this issue before any advice would be appreciated.
Solved! Go to Solution.
Hi @TommyBarnes @PanjiBrotoisworoIntrax @CherylWheeler11 ,
The fix for this issue is available on the production environment.
Thanks,
Ruth
Hi @Ruth_JiatengXu - I wonder, is there a similar problem this week. We are getting a timeout error on all our devices and surveys today. Are you aware of any issues?
My issue was caused by changes in Survey123. I had used an old survey as a starting point and the newest version of 123 didn't like some of the statements in the old survey. Once I started building from scratch in the current version of Survey123 connect the issues went away. the 504 error code seems to be a generic code that says something is wrong, but we don't know exactly what.
Hi @TommyBarnes ,
Thanks for your reply. If possible, please share your survey or XLSForm with us, my email is jxu@esri.com.
If not, could you try reproducing the error on our BETA website survey123beta.arcgis.com, and let us know the job ID? This will help us review the error log and investigate further.
Thanks,
Ruth
Does the issue occur in a newly created survey? If not, could you share your survey or XLSForm with us, my email is jxu@esri.com.
Thanks,
Ruth
My issue was caused by changes in Survey123. I had used an old survey as a starting point and the newest version of 123 didn't like some of the statements in the old survey. Once I built from scratch in the current version of Survey123 connect the issues went away and I was able to re-publish the survey with no issues.
The 504 error code seems to be a generic code that says something is wrong, but we don't know exactly what.
Thanks Ruth. It is odd because it seems to be first thing on a Friday morning 0800GMT, it all seems broken, but then, a couple of hours later (10am GMT) and doing nothing, it all works again. I wondered if there are updates that occur on a weekly basis with AGOL/S123 which may take time to take effect?
Hi @CherylWheeler11 ,
It looks like our server instance was down at that time but restarted automatically afterward.
Thanks,
Ruth