Select to view content in your preferred language

Power Automate triggers not working since 9th Oct

1062
13
Jump to solution
3 weeks ago
NigelCharman
Occasional Contributor

As per @michael_vetter's post in an older thread, our Power Automate flows stopped being triggered at about 00:00 UTC yesterday (9th October). I've created a new thread since this seems like a new issue.

We're not seeing any of the symptoms we saw with the previous trigger issue. The webhook still shows as Active on the ArcGIS REST Services page and the Notification Status table is empty.

The problem occurs both on our existing webhooks which have the "Response 200" workaround applied. These use the "When a record is updated in a feature layer" and the "When a record is created in a feature layer" webhooks respectively. It also occurs on new flows we created yesterday to try to debug the issue.

These flows should have been triggered 100+ times since yesterday but have not been triggered at all.

Currently it's only been reported by @michael_vetter and ourselves.

We saw some 503 errors before they stopped working. Other users have been getting 503 errors but their webhooks are still working.

Any thoughts on what we can try or how we can debug this @AnthonyLatini ?

1 Solution

Accepted Solutions
sosero
by Esri Contributor
Esri Contributor

This issue has been fixed as of now. Incase your Power Automate flows are not working as expected, please open a ticket with our team in Technical support and we can have a look at your Organization account. 

View solution in original post

13 Replies
JemGIS
by
Emerging Contributor

Following. This has also been occurring with us since the ArcGIS Online Hosted Feature Services Performance issues that occurred on October 7, 2024. Trigger has not fired successfully since Oct 7, 03:56 PM Eastern.

ahargreaves_FW
Frequent Contributor

Confirmed by us too.... This technology is incredibly unreliable. Ours hasn't fired since 10/7/24....

@AnthonyLatini 

@SeanKMcGinnis 

 

CatHeindel
Occasional Contributor

We are experiencing the same issue in Power Automate. We found that if we use the ArcGIS connector as a trigger for a Power Automate flow, the Power Automate Flow will not trigger. If we use the ArcGIS connector as an action in a Power Automate flow, the Power Automate flow triggers and the ArcGIS action executes as expected.

 

@AnthonyLatini 

@SeanKMcGinnis 

 

ahargreaves_FW
Frequent Contributor

@CatHeindel not sure I understand how to use the ArcGIS Connector as an action vs trigger?

0 Kudos
CatHeindel
Occasional Contributor

Your flow is triggered by an event in AGOL (create a feature, survey submitted, an attribute is update) vs your flow is triggered by, for example, an list is updated in sharepoint and later on in your flow you have an action in AGOL like create a record.

0 Kudos
tempeGisDev
New Contributor

We have the same issue on our hosted feature service webhooks and the Arcgis Power Automate Connector. By far this is one of the most unreliable products we have used. We are reaching out to file tech support tickets today and to our ESRI rep. Hopefully other folks can file tickets too or reach out to ESRI so we can get more visibility.

0 Kudos
SeanKMcGinnis
Esri Contributor

Good Day All - there has been an issue identified where some Power Automate flows are not being triggered by a feature service webhook. The team is aware of the issue and is working with multiple other product teams. From the troubleshooting that has been done, it is believed to be related to performance issues in ArcGIS Online which has impacted not only Power Automate, but also Make, FME, and ArcGIS for Python.

We are working towards a solution and will keep people posted as more information becomes available.

-sean
Sean McGinnis - ArcGIS for Microsoft 365 Product Manager
TL2
by
Frequent Contributor

Could this also be affecting the timeliness of a flow trigger?  We are using When a record is created in a feature layer and sometimes it takes over 10 minutes to trigger.

0 Kudos
NigelCharman
Occasional Contributor

Thanks for the fix! Our webhooks have been triggering the Power Automate flows for the last 90 minutes. 

0 Kudos