Survey123 Connection to Power Automate Issues

Question

We are not seeing new submissions to S123 triggering our Power Automate Flows.  Everything in the flow looks fine - connection is valid and show list of surveys, it saves ok, and we see a webhook in the survey123 website.  In the run history, we do not see the failed runs, but Power Automate indicates there is an error, and gives us this message:

Anyone else seeing this issue?

Derrick_Westoby · Answer

The recent update seems to have broken the webhooks.  After recreating webhooks (and enabling them for EDIT submissions), it seems to be working again in Power automate.  The flow is triggered on submission and the report is successfully generated (verified by viewing the recent reports window on the S123 website).

However, the flow is failing at the action just after generate report, which is an HTTP GET action to get the report.   It's failing IMMEDIETELY after the report action runs, and then it's failing.  It's failing because no URL was provided, and I  think that happens because power automate is no longer waiting for the report to finish generating.  (When the flow fails, I can see on the S123 website that the report is still in the process of being generated, and it succeeds 1 to 3 minutes after the power automate flow already failed because a URL was not provided).

@JamesTedrick @IsmaelChivite

Derrick_Westoby · Answer

I'm having similiar issues with survey123 forms/reports that are using power automate.   I recreated a webhook for one survey last week.  Another survey seems to have a functional webhook for some surveys, but not others.

JJ_Reyes · Answer

@wcozzens - what did you find out here? I noticed some of my Survey123 webhooks were randomly recreated on 11/5/2025. In Power Automate I was using the new ArcGIS trigger for survey submissions.

I'm also seeing Microsoft documentation that only the HTTP and Teams Webhook triggers need to be updated before Nov 30. https://learn.microsoft.com/en-us/troubleshoot/power-platform/power-automate/flow-run-issues/triggers-troubleshoot?tabs=new-designer

Any insights?