I have a survey I have been using and generating reports for years. Today I am seeing the following error:
Any thoughts what could be going on?
Hello @AndrewBowne,
There is a service disruption impacting the Survey123 report API at this time. We are monitoring the situation and will update when it has been resolved.
Is this particular outage isolated to today? Or has this been intermitent for the last ~2 weeks? I was away for the last couple weeks, and heard that something similar was happening on and off for that time.
Hello @abureaux,
This disruption is isolated to today. Is the error message observed the same ArcGISRequestError from the screen capture above?
Presently, my reports are just timing out without an error message...
(This is from Power Automate. The automation timed out after ~30 minutes)
Hello @AndrewBowne @abureaux,
We are seeing the report service slowly coming back online and are seeing successful report generation on our end. If you retry generating reports are you still seeing errors?
I am still seeing the same error this morning:
And a similar error in Make:
Is there anything that I need to do on my end?
Hello @AndrewBowne,
Based on the error message it looks like when the Survey123 report API is trying to communicate with your ArcGIS Enterprise Portal, the Survey123 report API is not trusting the connection. This could be a variety of reasons from the certificate the organization uses to the protocol the organization uses to communicate.
If you enter your Portal URL into https://www.ssllabs.com/ssltest/analyze.html (check on the box "Do not show the results on the boards") and run the test does the certificate come back as trusted and is TLS 1.2 enabled as a configuration protocol?
Hi Zach,
Thanks for the return message. I analyzed my portal URL and it returned that the certificate IS trusted and TLS 1.2 IS enabled.
I have two separate instances of Enterprise Portal running on two separate machines. One is 11.1 and the other is 10.9.1. Both of them are returning the same error.
I don't know if I mentioned this, but these surveys have existed for quite some time and we have never had an issue. This is something that has just recently popped up as an error.