ArcGIS Connector for Power Automate Premium does not trigger, does not return an error

JGardner_Verina

I have several flows set up to do the following steps:

1. Trigger when a new survey response is submitted
2. Generate a report from a .docx template using the submitted survey
3. Send an email to selected recipients with the generated report file attached

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:

• The "When a survey response is submitted" trigger is set to watch the correct survey.
• The ArcGIS connector is signed in to the correct account.
• The webhook is active in the survey settings, with all 'Event data' boxes checked, and Status set to 'On'.
• The report templates work correctly when generated manually from within Survey123.
• Flow checker has no errors.

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.

JGardner_Verina

Still an issue, still no flow trigger.

EDIT: Shortly after posting, we did the following:

1. Deleted the existing webhooks from the survey.
2. Opened the Editing view for the Power Automate flow, didn't make any changes but Saved it to refresh the webhook. Verified the new webhook in Survey123.
3. Updated the survey with new webhook on the mobile device and submitted a test survey.

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.