nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Power Automate Trigger Issue

DarraghOSullivan

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

Encontre mais publicações marcadas com

Accepted answers

All comments

abureaux

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?

Katie_Clark

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?

DarraghOSullivan

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

DarraghOSullivan

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!

Katie_Clark

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

AwesomeEvan

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 😛

DarraghOSullivan

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

RobertAnderson3

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.

AwesomeEvan

what do you mean it hadn't run before?

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

RobertAnderson3

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.

SamuelFirmenich

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.

studebakers_Boulder

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?

RickeyFight

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.

abureaux

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.

studebakers_Boulder

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 😞

abureaux

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...

TomFlahive1

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:

AdminPDM

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).

abureaux

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?

AdminPDM

I have refreshed the login credentials - it seemed to kill some of the other Power Automates that were still working though for other surveys.

After completely rebuilding the power automates they appear to be working (all but 1 image export - I can live without that one for the short-term).

Whenever I seem to "Edit" a power automate flow it throws an error on the initial trigger saying it cannot read the value for the survey123 selected. It then won't let me successfully check anything else in the flow as it doesn't find the initial survey. Is this something you have encountered? The only way to resolve this has been to delete the trigger and re-establish it which of course removes any dynamic links in the flow. Currently I'm at about a 2hr turn around to do this only to find out it is still failing with no real reason why.

abureaux

That is not something I have seen before, and definitely isn't working as intended.

I have seen it where the Initial Trigger changes the survey you select from the drop down from the human-friendly "Survey Name" to the back-end "Item ID". This happens when (and if) the Connection's login credentials time-out. Depending on which connection you are using, this happens every two weeks. If you go to your connections, refresh the login, and then go back into the survey to look at the Initial Trigger, it will automatically revert back to the human-friendly "Survey Name", which indicates the login information is valid.

Now... there is currently a bug, where the credentials for some specific operations are expiring every ~2 hours with Esri's built in ArcGIS Connectors. That is a known bug, and Esri is (theoretically) working on a fix. (this may be what you are running into... but it shouldn't affect "When a survey is submitted")

Are you using a Custom Connection, or the built-in Esri ArcGIS Connection? Also, AGO or Enterprise?

Jaivik_P

We are also facing the same issue with Power Automate flows. They were working fine since a year or so and suddenly stopped working (does not trigger 'When a survey response is submitted')!

The issue resolved when we re-established a connection reference. (Simply clicked on overflow menu (...) next to the trigger and clicked on a +New connection reference > then sign in to the account)

I also have noticed the similar behavior that @abureaux mentioned. The trigger would change back to human-friendly 'Survey-Name' after a new connection reference is set, which was before showing as an 'ItemID' of the survey.

If this connection time-out going to happen every 2-weeks or so, is there an automated way to re-establish/refresh that connection? Going in the backend and manually renew connection is not an ideal situation I guess!

abureaux

No. There is no a way to automate refreshing connections.

I (somewhat ironically) have a Power Automate flow and SP list set up to track Connections. I refresh connections once per week, and record that in SP. Failure to record the refresh results in notifications after 8 days. That way, my connections are never out of date and processes aren't affected.

How I refresh Connections is as follows:

I'm in Power Automate almost every day and this action is barley a few seconds, so it isn't terribly disruptive to my workflows.

Making a new connection works as well, but then you end up with tons of dead and dying connections on this page (Hence why my primary Connection that hundreds of flows are based off has a "3" in its name! When I first started in Power Automate, I remade several connections before I realized what was happening).

Jaivik_P

You are right @abureaux, Creating New connection reference (although it resolved the issue), generates several extra connection references.

Instead, the easy way around is to setup a reminder for every 2-week to check the Connection itself - whether it needs a re-connect.

TomFlahive1

Yes, I've had a weekly Monday morning reminder myself to refresh the Survey123 connection in Power Automate for some time now. I do it weekly in case I forget a week. It only takes a minute.

When I was at the Developer Summit this year, I talked to one of the Esri developers about this. My recollection it that he said the Survey123 actions in Power Automate were going to be replaced with ArcGIS actions (the ones with orange icons) that can also handle Survey123. Apparently the Survey123 specific actions use an older approach/technology that has certain drawbacks, such as this need to refresh the connection manually. I thought that was going to happen this year, but I haven't seen it yet. We'll see.

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.