topic Re: Power Automate Trigger Issue in ArcGIS Survey123 Questions

Power Automate Trigger Issue

DarraghOSullivan — Wed, 11 May 2022 12:26:10 GMT

Hi all,

I've had 4 Power Automates working with Survey123 for a long time, but I just noticed that they have failed in the last few days. It's a problem with the trigger, where I get the message:

The 'Location' header is missing in the response of subscribe request.

Has there been any change within Survey123 that would be causing this? The survey responses are working fine with data going into the Feature service etc. Surveys created in Connect, submitted online, with location of survey response fed via url parameters into the Survey.

Thanks, Darragh

Re: Power Automate Trigger Issue

abureaux — Wed, 11 May 2022 17:58:02 GMT

I just double-checked and all of my Automations are working properly.

Did you update your accounts password/let it expire, or make any changes to your Portal?

Re: Power Automate Trigger Issue

Katie_Clark — Mon, 23 May 2022 20:10:05 GMT

I am having this exact same issue! I haven't changed anything, and all of a sudden none of my flows are working.

Did you ever figure out what was going on, and find a solution?

Re: Power Automate Trigger Issue

DarraghOSullivan — Tue, 24 May 2022 01:01:20 GMT

No, I had made no changes at all, just stopped working all of a sudden.

Re: Power Automate Trigger Issue

DarraghOSullivan — Tue, 24 May 2022 01:02:22 GMT

No I never figured it out. I decided to re-build all the flows to be sure! Took time but they are working ok since then... Hope you find an easier solution!

Re: Power Automate Trigger Issue

Katie_Clark — Tue, 24 May 2022 13:59:18 GMT

Shoot, that's disappointing. Thank you for responding though! 🙂

Re: Power Automate Trigger Issue

AwesomeEvan — Fri, 15 Jul 2022 02:32:22 GMT

I just started getting this issue as well...

Sry, NOT Sry, but I found a much easier way to resolve this.

Save the broken flow as a new flow... then turn off your old broken one... Voila!

I found this post first then luckily got this fix first rando try 😛

Re: Power Automate Trigger Issue

DarraghOSullivan — Fri, 15 Jul 2022 05:07:32 GMT

Smart and simple! Will remember that for next time... 🙂

Re: Power Automate Trigger Issue

RobertAnderson3 — Tue, 25 Oct 2022 14:32:44 GMT

I just encountered this as well, making a copy didn't solve my problem as it was a survey that hadn't run before. I'm going to try a complete remake but that's silly, wanted to add my voice so Esri knows it's an issue.

Re: Power Automate Trigger Issue

AwesomeEvan — Tue, 25 Oct 2022 14:50:07 GMT

what do you mean it hadn't run before?

that makes it sound like its not the same issue as missing location header

Re: Power Automate Trigger Issue

RobertAnderson3 — Tue, 25 Oct 2022 17:18:44 GMT

It had no previous runs in the history, I thought it had months ago when this project first came up but none were in there. When I looked into it saying 'there might be an issue' it did show me the Location header error message.

I re-made it again (and made sure to update my survey on my device to fix the webhook link) and it worked though.

Re: Power Automate Trigger Issue

SamuelFirmenich — Wed, 02 Nov 2022 12:51:07 GMT

I found that if you turn the flow on and off in Power Automate, the web hook will reappear in the Survey123 settings. For some reason, the web hook was not there when the flow was on previously. I believe it was related to the connection (credentials) being broken.

Just to be sure, check the "My connections" for the Survey123 trigger step and make sure you're connected. Also, update the form or reopen the form in the web after you save and the changes are made.

Re: Power Automate Trigger Issue

studebakers_Boulder — Mon, 28 Nov 2022 19:08:22 GMT

I too just discovered that the same error was preventing my previously successful flows to suddenly fail. I checked all connections in PA and webhooks in Survey123 - all were good. No changes were made on either the PA or Esri enterprise side which might have caused this issue. To rectify, I had to 'Save As' to create a new flow - no other changes were made to the 'new' flow.

Any possible explanations from the Esri side as to why this might be happening?

Re: Power Automate Trigger Issue

RickeyFight — Thu, 02 Feb 2023 22:09:12 GMT

I ran into this issue on 1/27/2023. I am not sure why it is failing. I have tried saving as and creating a new flow. Both ways dont work.

Re: Power Automate Trigger Issue

abureaux — Wed, 19 Jul 2023 22:55:23 GMT

Okay. I just had this happen to me!

I tried looking at a bunch of different things, and I can safely say that I have no clue why they stopped working. For me, it was July 11, 2023.

I tried the obvious things like turn it off and back on. No luck.
I tried making a new flow, and bam. New flow magically worked.
I compared the old flow and the new flow, and they were identical with the exception that the new flow triggered and the old flow didn't... or so I thought
I checked again the following day, and the old flow began working properly after the new flow was turned on (so now I have two working webhooks/flows).
This got me thinking... I went to another flow that wasn't working, found a previously successful flow run, and hit "Resubmit". The flow ran as it should, and this magically "jump started" the trigger to act the way it should, thus fixing my flow.

Now, I am going to have to make a flow that queries the Portal to compare flow runs against database entries to ensure this doesn't happen again...

Esri doesn't seem to have any information on this issue (at this time). Hard to say if it's an Esri or PA issue.

Re: Power Automate Trigger Issue

studebakers_Boulder — Thu, 20 Jul 2023 16:10:23 GMT

Regardless of whether the issue is with Esri or PA it makes using the two together unreliable - I can't continue using them without some sort of explanation or understanding 😞

Re: Power Automate Trigger Issue

abureaux — Tue, 01 Aug 2023 20:34:48 GMT

So I've been noticing this more. Still no clue why it's happening.

But I have found that the issue is now happening when I resave a flow with the "When a survey response is submitted" step. After saving, the flow becomes none responsive. But it wakes up again after I force through a previous submission...

Re: Power Automate Trigger Issue

TomFlahive1 — Fri, 29 Sep 2023 00:27:50 GMT

I don't know if this is a solution to the original problem described, but it is related to a Power Automate trigger not working with a Survey123 App. Since I came across this post while looking for a solution, I thought I would share.

We had created a Survey123 App and wanted to use Power Automate to notify us when new records were added. When we originally created the Survey123 app, Survey123 set up a base feature layer (1) as well as two views on that layer (2, 3):

We originally created our trigger to point to the base layer (1). But the trigger was not firing when we added new records using the Survey123 form. After working with an Esri support analyst, he determined that it was the _form view (2) that was actually getting called when a new records was added to the survey. So we switched the trigger to point to that "_form" view (2) instead of the base layer (1). We had to make one more tweak to get this to work. Although the base layer had the "Keep track of changes to the data" setting checked, the _form view did not. So we check that setting on the view as well:

Once we did that, the trigger began to fire when a new record was added.

Here is what the start of the workflow looks like:

Re: Power Automate Trigger Issue

AdminPDM — Wed, 06 Nov 2024 22:02:57 GMT

So I have several flows that we use to generate reports - some randomly stop working where simply going in, saving a copy and restarting the flow (after resetting the trigger and all dynamic links) get the flows going again. I have encountered the problem where the flows do not trigger at all - i know the connections are good as I have other flows using the same connections that still work and run.

Given this PowerAutomate to Survey123 system seems flakier than a good puff pastry does anyone know of any other work around without costing me half a credit each time i need to generate a report (we generate about 30 reports a day).

Re: Power Automate Trigger Issue

abureaux — Wed, 06 Nov 2024 22:06:09 GMT

Can't help with the credits, but as for the connections, they should be a lot more stable than what you are describing. While there are issues, they are relatively few and far between. I generate hundreds of reports a day.

Have you tried refreshing the login credentials for the connections in the Connections tab of Power Automate?