topic Re: flow with ArcGIS connectors stopped working in ArcGIS Connectors for Power Automate Questions

flow with ArcGIS connectors stopped working

NataliyaLys — Wed, 31 Jul 2024 16:10:51 GMT

Some of my flows stopped working this morning (7/31) around 8am. Most of them have not been modified in months. I cannot figure out why they wouldn't run when I trigger an update. These are critical flows for us, as we use those to commicate with citizens/employees about our 211 reports, as they get updated.

I just opened a ticket with ESRI. But also posting here perhaps anyone here have some insight? @SeanKMcGinnis , @AnthonyLatini Was there an recent update to ArcGIS connectors or AGO?

Appreciate any help.

Nataliya

Re: flow with ArcGIS connectors stopped working

RobertAnderson3 — Thu, 01 Aug 2024 11:53:21 GMT

We had issues with some overnight too, we refreshed our credentials on the connector and they seem to be working again, have you tried that?

Re: flow with ArcGIS connectors stopped working

NataliyaLys — Thu, 01 Aug 2024 21:29:58 GMT

@RobertAnderson3 Thank you for the suggestion. Yes, I tried that and got some of the flows to work. But then they stopped working again. And the flows have been randomly working here and there, more often not working then working. I'm working with support now, had two calls, but no solution yet.

Re: flow with ArcGIS connectors stopped working

RobertAnderson3 — Fri, 02 Aug 2024 17:19:02 GMT

Darn, that's such a pain. Please keep us posted on any solutions of information you get from support!

Re: flow with ArcGIS connectors stopped working

cepsgis — Fri, 02 Aug 2024 23:27:38 GMT

I'm having a very similar issue. I keep getting told I have an invalid redirect URI. @SeanKMcGinnis , @AnthonyLatini any suggestions.

Re: flow with ArcGIS connectors stopped working

NigelCharman — Tue, 06 Aug 2024 09:53:23 GMT

We've been seeing the same behaviour. Our flows have been working for months and now only work 5 or 6 times before stopping. This started around 31/7.

The flow can be restarted by stopping and starting it (which sets up a new webhook).

After restarting the flow, the Webhook Info in the ArcGIS REST Services Directory shows Active = True.

After 5 or 6 occurrences, it shows Active = False and the Power Automate flow is no longer triggered.

Notification Status shows:

Invoked Timestamp	Invoked Successful?	Server Response
1722919397046	No	Accepted
1722922711316	No	Accepted
1722924234883	No	Accepted
1722924322882	No	Accepted
1722925670649	No	Accepted
1722925961796	No	Accepted

Re: flow with ArcGIS connectors stopped working

RobertAnderson3 — Tue, 06 Aug 2024 11:36:12 GMT

I wonder if it's a similar issue to this thread? The OP on that thread has had BUG-000169725 attached to their case.

https://community.esri.com/t5/arcgis-for-power-automate-questions/power-automate-drops-both-azure-and-adfs/m-p/1515080

Re: flow with ArcGIS connectors stopped working

RobertAnderson3 — Wed, 07 Aug 2024 14:24:13 GMT

I just discovered another flow that I have had issues with like this, since July 31st at 10am Atlantic time it has not worked, I have refreshed the connections in this time but it hasn't triggered the "when a feature is updated in a layer" since 9:56am, the next edit was 10:07am and it hasn't triggered in a week now.

EDIT: So while the reset of the credentials didn't work, I noticed on my trigger that the selected layer was showing it's ItemID, I repicked it from the dropdown list of layers and it seems to be triggering again. However, the feature updates that happened between 9:56am July 31st and today (August 8th) at 10:52am when I updated my flow did not register at all and I have to deal with those manually.

Re: flow with ArcGIS connectors stopped working

NataliyaLys — Wed, 07 Aug 2024 15:39:37 GMT

Still having issues here.

On one of the calls with Esri they pointed out that selected layer was showing ItemID (instead of the layer name), just like @RobertAnderson3 mentioned. I reselected layer name from the list and saved. The flows worked a couple times, and then stopped working again.

Some other things I tried:

I tried saving a copy of my flows, and the new (copy) of the flow would run at first, a few time. But then it stopped working as well.
I would stop (turn off) my flow, then I will go and refresh ArcGIS connection, and then I will start (turn on) my flow, then I would go and make edits and the flow would trigger most of the time. But this is not sustainable.

Re: flow with ArcGIS connectors stopped working

TL2 — Wed, 07 Aug 2024 18:16:52 GMT

I am having issues with ArcGIS and Survey123 connectors.

Re: flow with ArcGIS connectors stopped working

BigLouC — Wed, 07 Aug 2024 21:57:17 GMT

We were also notified that our flow stopped sending messages. Apparently the webhook was set active to false. There was no edited timestamp. I updated the status to active true and sent a test. It worked and message was sent. Same thing, the last message was sent out 7/31 at 7:15am, nothing after that until my test today. Hopefully someone at ESRI replies.

Re: flow with ArcGIS connectors stopped working

NigelCharman — Wed, 07 Aug 2024 22:02:45 GMT

Keep your eye on them. We're finding that they work 5 or 6 times after a restart and then stop again.

Re: flow with ArcGIS connectors stopped working

NataliyaLys — Thu, 08 Aug 2024 17:22:49 GMT

@BigLouC thank you for the info. I checked my webhooks, and noticed the same issue: Active was set to false?! I'm reactivating them all and see how my flows work going forward. I will report back.

Re: flow with ArcGIS connectors stopped working

michael_vetter — Thu, 08 Aug 2024 18:09:09 GMT

I'm having the same issue as everybody else. I noticed the Active setting was set to false so I reactivated it, but unfortunately it some how sets itself to false after a handful of flows. I've submitted a ticket with ESRI, but the support analyst is saying she can't reproduce this issue.

Re: flow with ArcGIS connectors stopped working

TL2 — Thu, 08 Aug 2024 18:11:13 GMT

Where do you set the Active Status?

Re: flow with ArcGIS connectors stopped working

michael_vetter — Thu, 08 Aug 2024 19:43:13 GMT

On the feature layer, scroll down to the URL section and click View. On the next screen click Admin at the top right which should then show a WebHooks link. Click the WebHooks link and you'll see all the web hooks associated with the layer. There are some supported operations (screenshot below) so click Activate All then click the Activate All button.

Re: flow with ArcGIS connectors stopped working

NataliyaLys — Thu, 08 Aug 2024 21:37:58 GMT

Tried resetting the Webhook status Active = True, but after a few runs it switches back to Active = False.

Re: flow with ArcGIS connectors stopped working

AnthonyLatini — Fri, 09 Aug 2024 00:55:02 GMT

Hello @TL2 @NataliyaLys @michael_vetter @NigelCharman @BigLouC - Thank you for posting this information. We have a number of reports of this issue and are attempting to pinpoint the root cause of this error.

As a note, there have been gradual rollouts of the ArcGIS connectors over the last few weeks with the last of this phase being the ArcGIS Enterprise connector. The ArcGIS connectors started this process during the week of the 2024 User Conference (roughly July 17th, 2024). We are trying to determine if there is a correlation between this deployment and the issues that everyone in this thread is experiencing on July 31st since that would put it at a 14-day token expiration period.

Please bear with us as we try and solve this issue! Thank you for your patience!

Re: flow with ArcGIS connectors stopped working

AnthonyLatini — Fri, 09 Aug 2024 00:58:45 GMT

Hiya! So for this error, you may need to modify the application that was created in your ArcGIS Enterprise instance. Please ensure you have the following URIs set in the application in your content.

Also - I am assuming that you are on Enterprise since it is asking for redirect URIs. 😀

Re: flow with ArcGIS connectors stopped working

michael_vetter — Fri, 09 Aug 2024 14:44:51 GMT

That's the same behavior that I'm experiencing. I periodically check the settings and reactivate the webhook if needed. I know it's a terrible workaround, but until the issue is resolved it's the best solution I've found.