Power Automate triggers not working since 9th Oct

[NigelCharman]

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 ?

[LeviCecil]

Hi Kathryn,

It's a hosted feature layer, and I'm almost certain I didn't publish it from reference. But I could be wrong. Is there a better way to publish it? This bug is from July. Any idea when it will be fixed?? 

[KathrynWalker]

Hi @LeviCecil,

That bug is in product plan, meaning it is set to be fixed in the near-term (next release or two). 

I would confirm the service URL for the item in the organization. Not just from the item's overview page. Does it say 'MapServer' or 'FeatureServer' within the URL?

Thank you,
Katie

[LeviCecil]

It is definitely a feature server. How long is near term? We're about to ditch Power Automate altogether and find or build a custom solution. The ArcGIS triggers have never worked the way they are supposed to. We also tried Make, and that was worse. 

[KathrynWalker]

Apologies for any frustrations. I'd recommend getting in touch with Esri Support to gather more details and troubleshoot the behavior further. 

Thank you,
Katie 

[LeviCecil]

Well it turns out I had two versions of the dataset, one hosted and on not. 😅 I switched to the hosted version and the trigger is working.