Answered

ArcGIS/Survey123 Flow failing

(1) Share

Report

Posted on by cymorg

128

I have an ArcGIS/Survey123 form that uses a webhook to trigger a Power Automate flow. This has been working perfectly for months then it suddenly stopped working. Nothing has changed at either end... more accurately, something must have changed but the change was not instigated by anyone in my org.

The form still sends its payload to the Flow. The flow is triggered but the next step (a simple Parse JSON) fails with something like... expected int, got string. The schema has not changed, the payload didn't change, all values are correct etc.

However, I notice that the trigger previously displayed the name of the Survey123 form and now displays a unique ID and the dropdown won't list the other Survey123 forms as it should. This suggests the Survey123 connector used by my flow has "forgotten" how to connect to Survey123. Adjusting the connector by re-entering credentials did not resolve the problem.

So, why would a Survey123 connector just stop working?

I recreated the Flow (which creates a new webhook in the Survey123 form settings) and the new flow is working fine but as I can't explain why the previous flow stopped working I fear the same thing could happen again. Is this just another "pray to the Microsoft gods and have faith" thing, or can someone tell me how to identify the real root cause?

Thanks

Categories:

General topics

I have the same question (0)

All responses (8)

Answers (1)

manuelstgomes 6,625 on at

Like (0)

Report
Copy link

Link copied!

Hi @cymorg1

I just stumbled on this request, but it's been a while that you submitted it. Were you able to fix it?
If so, how did you do it so that the community can benefit from your findings?

If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Cheers
Manuel

Was this reply helpful? Yes No
Verified answer

cymorg 128 on at

Like (0)

Report
Copy link

Link copied!

My resolution was to delete my Flow and recreate it, including a new connector to ArcGIS/Survey123. That doesn't instill confidence in the platform. To date, this is an exceptional case - let's hope it stays that way.

Was this reply helpful? Yes No
Ben_C_GIS 12 on at

Like (0)

Report
Copy link

Link copied!

Edit: I fixed it by initiating a new connecting to Survey123/re-authenticating as you described. I failed to understand what you meant before, but now under "Connectors" in the ellipsis' dropdown menu of the Survey123 trigger it lists "Survey123" twice, however only the 'new' one is checked. I agree that while this fixed it, it makes me nervous and not confident in this connection. Thanks!

I have the same strange thing happening to me, however I discovered this when creating a new flow to a new Survey123 form so "deleting it and starting over" doesn't really apply.

My existing flows still function all the way through their other actions unimpeded, but also have this long alphanumeric code instead of the drop-down menu of existing Surveys in my AGOL content.

Anyone got any solutions? Kinda need this to work...

Was this reply helpful? Yes No
Ben_C_GIS 12 on at

Like (0)

Report
Copy link

Link copied!

Unfortunately this doesn't work if you encounter this error while creating a new flow in the first place, which is the case for me.

Was this reply helpful? Yes No
Patmac0012 4 on at

Like (1)

Report
Copy link

Link copied!

Has anyone solved this issue, or have an update?

I am also having the same issue. Where the survey name changes from the name I assigned, to a long alphanumeric string. Once the change happens, the flow no longer works.

The only solution I have found is to export the flow, then import the flow right back. I read another thread that said the issue may be related to this being flow being created using the "trigger event" template. And maybe building a custom flow not using a template will solve this issue. However I have not tried this solution yet.

I agree, this defeates the purpose of this being automated.

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

have been looking for a workaround to this same issue for a few days.

My flow shows that the create report is working but when I attempt to upload the file from URL to Onedrive it fails giving an error code 400. This step utilized the option for dynamic text - URL from final result with the survey123 connection.

Next I tried to just enter in the same code output('create_report')?['body/resultinfo/resultinfo/resultfile/url'] that is utilized within that dynamic content option and it then at least recognizes that there is a source URL but the ? in that code give error 401 "Action 'Upload_file_from_URL_2' failed"

I took the ? out and it failed with a 404 error which still shows that the source URL was identifiable but no resource could be found.

I then just entered in the URL for the layer itself and the entire flow worked but the file found in onedrive was unformatted, when I opened it in work it was just the metadata to the layer itself an nothing from the survey submission.

I cannot seem to get this to work, I have already attempted the reconnection to the connectors being used, and have deleted and recreated this new flow a few times thinking it was something hung up somewhere.

suggestions?

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (2)

Report
Copy link

Link copied!

Good afternoon. I experienced this issue with a Flow that had been working just fine when a new update was rolled out.

I was able to troubleshoot and have things up and running again pretty quickly. Here's how:

1. Under Data > Connections, I clicked on the three dots next to the connection for Survey123 and chose "Switch account" . I then entered my credentials.

Unfortunately, this did not fix it. So, I proceeded to this next step.

2. Under My Flows, I clicked on the three dots next to the Flow I needed and chose "Export Package (.zip)". Within the export window, I clicked on the wrench under Action for the Survey Name and chose "Create as New".

3. Then, under My Flows, I chose Import Package (Legacy), and uploaded the flow I had just exported. During the import process, I provided a new name to the Flow and re-established my connections to Office 365 Outlook and Survey 123. Then, I turned the old (non-working) flow off, and turned the new flow on.

Success! I hope that this helps someone else.

Was this reply helpful? Yes No
KR_LVWD 3 on at

Like (0)

Report
Copy link

Link copied!

This workaround actually worked for me! Thank you i hope i don't have to be doing this often though.

Was this reply helpful? Yes No