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; } } }

Flow mit ArcGIS Connectors funktioniert nicht mehr

NataliyaLys

Einige meiner Flows funktionieren heute Morgen (31.07.) gegen 8 Uhr nicht mehr. Die meisten von ihnen wurden seit Monaten nicht mehr geändert. Ich kann nicht herausfinden, warum sie nicht ausgeführt werden, wenn ich ein Update auslöse. Diese Flows sind für uns kritisch, da wir sie verwenden, um mit Bürgern/Mitarbeitern über unsere 211-Berichte zu kommunizieren, sobald diese aktualisiert werden.<\/P>

Ich habe gerade ein Ticket bei ESRI eröffnet. Poste aber auch hier, vielleicht hat jemand hier Einblick? @SeanKMcGinnis<\/a> , @AnthonyLatini<\/a> Gab es ein kürzliches Update der ArcGIS Connectors oder AGO? <\/P>

Ich schätze jede Hilfe. <\/P>

Nataliya<\/P>

Finde mehr Beiträge mit dem Tag

Accepted answers

AnthonyLatini

@BigLouC @NataliyaLys @MichaelTorbett @fitzpat_s @Scott_Sambell - Good evening, all. Thank you for your patience on this issue. We have found the root cause of the issue and I have detailed it in the following post.

I have written a post about this located here with a quick fix until it is patched by the ArcGIS Online team: 8/15/24: Update and quick fix for issues with Webh... - Esri Community

All comments

NigelCharman

@michael_vetter @NataliyaLys , I've created a new thread for this new issue - https://community.esri.com/t5/arcgis-for-power-automate-questions/power-automate-triggers-not-working-since-9th-oct/m-p/1547461#M782

NataliyaLys

My flows are triggering, but I have been getting some 503 error on 'Fetch updates...'. Got several errors today.

michael_vetter

I'm seeing the same thing. I checked some of flows that don't use any triggers from the ArcGIS connector and they worked as expected.

NigelCharmanPre-Prod

My flows also stopped working about 00:00 UTC. Prior to this, I saw some 503 and 502 errors about 20:00 UTC. I then made some changes and they worked at about 21:30 UTC. I've now created some new simple flows and can't get the webhooks to work with those either.

The REST Services Directory shows that they are Active. Unlike last time they started failing the Notification Status shows an empty list.

Scott_Sambell

Hi Michael. Sorry i don't use Flow at all. We connect to webhooks with FME. All i know is that the webhooks are still active and they are accepting 202 responses.

michael_vetter

Scott,

Thanks for the reply. I checked the status of my webhooks and they're still active, but they aren't being triggered today. Do you know of any troubleshooting that I can do to help identify the issue?

Scott_Sambell

You don't need the workaround anymore as the patch has been released.

To check to see if your webhooks are still active, go to the REST Services Directory and check on the Webhook Info page that Active : True

Mine are still active this morning (i have scheduled report that runs every morning in case this ever happens again)

michael_vetter

I just noticed that none of my flows have been triggering today. I have the status response 200 workaround in my flow and they were working fine until today. What troubleshooting steps can I take to make sure that this isn't another bug in the connector?

AnthonyLatini

Hi @Scott_Sambell - I have replied to your private message.

For those using FME, another contributor on the forums posted this response as a fix for FME.

Scott_Sambell

Hi @AnthonyLatini Should i start a new topic for this? I just got another notification that my issue was "resolved" and there has been no progress on the issue i raised several weeks ago, which is still majorly affecting our work with several clients. I've tried messaging you direct with no response. Not sure what else i can do.

BigLouC

Thanks Anthony.

Applied it on Friday, ran without issues on Saturday AM. It has been running fine since.

Thanks again.

MichaelTorbett

Anthony,

I applied the quick fix Friday morning and there hasn't been any issues since.

Thank you for the update!

Michael

Scott_Sambell

What about FME @AnthonyLatini ? We don't use Power Automate. This is affecting anything that returns a 202 response. (as we mentioned on the 9th August)

AnthonyLatini

I have written a post about this located here with a quick fix until it is patched by the ArcGIS Online team: 8/15/24: Update and quick fix for issues with Webh... - Esri Community

BigLouC

In case anyone is interested, https://support.esri.com/en-us/bug/webhooks-fail-to-trigger-when-using-arcgis-connectors-f-bug-000169874

That is the bug that I believe Michael opened. As per the details, it should be fixed in the next or two later releases. Dont know what that means, but there is no workaround that I can see other than manually updating the status.

MichaelTorbett

Having the same exact issue and opened up a case with ESRI. They informed me it's a bug. Any ETA when this will be resolved?

BigLouC

Good morning Anthony,

Any update on this issue? Is there a workaround that we can use? I have not seen any mass communication on this issue, bug release, etc.

fitzpat_s

We have been experiencing similiar issues. Our premium connector has been failing since 31st july too. We have reset the connector andpushed the edits through via ArcGIS pro - this worked initally but then the connector stopped working. Its not triggering a fail on the flow, just not triggering.

Also having issue in a survey 123 connector failing since 31/07

Scott_Sambell

We are seeing the same thing on 5 of the AGOL portals we manage. It is not affecting the webhooks that use 'Make' but all of the webhooks that use FME are switching Active from True to False after a response. These webhooks are integral to many of our systems and we are struggling to keep them going while Esri find a fix or a workaround. If it helps at all - 'Make' responds with a '200 OK' response and FME with a '202 accepted" response. We assume the 202 is somehow causing the webhook to switch Active to False and that it was something that Esri did on 1st Aug when everything suddenly stopped working

RobertAnderson3

@AnthonyLatini I have some flows with ArcGIS actions that still seem to work fine, using the same connection, it's only the flows I have that are triggered by the ArcGIS connection that I can't get to run, and it doesn't give me any errors (though it seems others might be having a different experience so I'm not sure if that helps).

RobertAnderson3

Thank you for outlining the steps here, I just looked and yes it's the same thing for me here as well. It seems it only adds webhooks here if they're the trigger, not if there is an action in a flow that queries the layer.

I have a few flows with actions in them for the ArcGIS Online connector that are still working normally, however the one I have with the ArcGIS trigger doesn't run at all.

RobertAnderson3

Yup, I just checked this morning and they stopped running almost immediately after I was done looking at them on Wednesday, the last time it ran was 12:00pm (Noon) Atlantic time. I'm currently talking to Esri Support as well.

BigLouC

The same thing happened to me today. I updated the Active=True last night. It ran today one time and it stopped. I checked the webhook and it was False. I updated it and the messages started again.

Hopefully as per Anthony, they find a solution or a workaround as we have inspectors that are relying on these messages on a daily basis.

michael_vetter

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.

AnthonyLatini

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

AnthonyLatini

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!

NataliyaLys

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

michael_vetter

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.

TLongSUGF

Where do you set the Active Status?

michael_vetter

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.

NataliyaLys

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

NigelCharman

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

BigLouC

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.

TLongSUGF

I am having issues with ArcGIS and Survey123 connectors.

NataliyaLys

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.

RobertAnderson3

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.

RobertAnderson3

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

NigelCharman

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

cepsgis

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

RobertAnderson3

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

NataliyaLys

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

RobertAnderson3

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?

Nimm an der Unterhaltung teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

Alle Communities
Neueste Beiträge
Gefolgter Inhalt
Community-Hilfe

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