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 ?
Solved! Go to Solution.
So what was the fix??
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.
@SeanKMcGinnis and @sosero thank you for replying and letting us know there was an issue. I started seeing Power Automate flows triggering again as well.
This will be a long shot, but do with either of you know if there is a way to access a web hook's log on the AGOL side. I do not see option for a log on the REST service page? Both times when the web hooks went down, I was blind in trying to figure out if the issue was on the AGOL side or Power Automate side. Thank you - Cat
@CatHeindel - as of today, I do not think there is a way to review webhook logs.
I use WebHook.site to set up helpers allowing me to log when webhooks are firing for my critical flows. This allows me to understand the source of the issue - is it Power Automate causing the issue or is it something further upstream and the webhook is not firing.
@SeanKMcGinnis Thank you!! I will give your suggestion a try
Hi All, I am having trouble with Webhooks to AGOL. I am getting the webhook error here:
In finding this and other blogs, it seems like it is related. All layers I have tried have tracking enabled, I have tried setting other permissions, and have even gone so far as using only layers out of my admin account. My situation differs from Cat's in that this is my first go at a PA AGC where I am fetching fields. My PA script to email me when a record is created works, but just not the field fetch. Since I have never had it working, I am not 100% confident if I am doing something wrong or if there is a flaw. It appears that it cant read the fields because the JSON isn't being returned properly. Can you guys help?
I am getting the same error
We have seen a few reports of similar behavior with webhooks in Power Automate and the error message:
Power Automate error message: Flow save failed with code 'DynamicOperationRequestClientFailure' and message 'The dynamic operation request to API 'arcgis' operation 'GetFeatureLayerResponseSchemaForWebhook' failed with status code 'NotFound'.
Some individuals have found improvement with their webhooks as of this morning.
If you are still seeing issues, would you be able to confirm if you are the error message above, share the feature service URL with me (can share here or private message me), and if there is a joined view layer with an area of interest defined?
Thank you,
Katie