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

Les déclencheurs Power Automate ne fonctionnent plus depuis le 9 octobre

NigelCharman

Selon @michael_vetter dans un post dans un ancien fil, nos flux Power Automate ont cessé d'être déclenchés vers 00:00 UTC hier (9 octobre). J'ai créé un nouveau fil car cela semble être un nouveau problème.<\/P>

Nous ne constatons aucun des symptômes que nous avions vus avec le problème précédent de déclencheur. Le webhook apparaît toujours comme Actif sur la page ArcGIS REST Services et la table Notification Status est vide.<\/P>

Le problème se produit à la fois sur nos webhooks existants qui ont la solution de contournement "Response 200" appliquée. Ceux-ci utilisent respectivement les webhooks "When a record is updated in a feature layer" et "When a record is created in a feature layer". Il se produit également sur les nouveaux flux que nous avons créés hier pour essayer de déboguer le problème.<\/P>

Ces flux auraient dû être déclenchés plus de 100 fois depuis hier mais n'ont pas été déclenchés du tout.<\/P>

Pour l'instant, cela n'a été signalé que par @michael_vetter et nous-mêmes.<\/P>

Nous avons vu quelques erreurs 503 avant qu'ils ne cessent de fonctionner. D'autres utilisateurs ont reçu des erreurs 503 mais leurs webhooks fonctionnent toujours.<\/P>

Avez-vous des idées sur ce que nous pouvons essayer ou comment nous pouvons déboguer cela @AnthonyLatini ? <\/P>

Trouver plus de publications taguées avec

Accepted answers

sosero

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.

All comments

JemGIS

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

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

@AnthonyLatini

@SeanKMcGinnis

CatHeindel

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

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

CatHeindel

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.

tempeGisDev

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.

SeanKMcGinnis

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.

TLongSUGF

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.

NigelCharman

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

sosero

CatHeindel

@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

SeanKMcGinnis

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

CatHeindel

@SeanKMcGinnis Thank you!! I will give your suggestion a try

LisaT

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?

AJD

I am getting the same error

Katie_Walker

Hi @AJD and @LisaT,

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

DustinEdge_Boroondara

So what was the fix??

LeviCecil

Hi @KathrynWalker I was having trouble with my Enterprise 11.3 connections due to BUG-000169725

I created a new connection and was able to save my flow. Now I'm having similar issues as described above. When a record is created in a feature layer is not working as a trigger.

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

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