I have several flows set up to do the following steps:
This used to work reliably. Recently, we had recurring problems and errors using the older Survey123 Connector for Power Automate, so we have paid for Power Automate Premium to be able to use the premium ArcGIS Connector.
Now, the flows do not trigger at all when surveys are submitted. There are no error messages, and the event does not appear in the run history. The new record appears in the survey data as expected. I first encountered this issue several weeks ago and set it aside, hoping it was a fluke. Today, after verifying that the AWS outage issue seems to be resolved, I still cannot get the flows to trigger. This is true both when testing the flow from the Edit view, and when the flow is switched on. I have checked the following conditions:
This has been very problematic to troubleshoot, as neither Esri nor Power Automate register any error. The two services are simply not talking to each other at all.
Solved! Go to Solution.
Still an issue, still no flow trigger.
EDIT: Shortly after posting, we did the following:
As of now, with the above changes, the webhook triggers successfully. The previous webhook was definitely set to the same connector, from the same flow, but it must have somehow become bugged or out of sync with the connector.
I have had a similar problem with webhooks not seeming to be firing. I wonder if these are all backed up in a massive queue waiting to execute.
This morning a PowerAutomate flow was triggered which is supposed to run when a new record is created. It contained records that have a creation date that is more than 3 day ago, so a huge delay in the webhook firing.
Another data point with ArcGIS webhooks not firing:
https://community.esri.com/t5/arcgis-connectors-for-power-automate-questions/arcgis-connectors-broke...
I wonder if this might not be due to AWS issues, but that ArcGIS Online was updated yesterday?
FWIW my legacy Survey123 connectors/webhooks are continuing to fire successfully.
Is this still an issue for you? I just tested this trigger and it is working for me.
Still an issue, still no flow trigger.
EDIT: Shortly after posting, we did the following:
As of now, with the above changes, the webhook triggers successfully. The previous webhook was definitely set to the same connector, from the same flow, but it must have somehow become bugged or out of sync with the connector.