Okay, ich versuche wirklich zu verstehen, warum einige meiner Flows funktionieren und andere nicht. Ich habe ein paar Flows, bei denen ich versuche, eine Nachricht in Teams zu posten, damit die PMs wissen, wann Daten gesammelt werden. Dieses erste Bild meines Workflows postet korrekt. Dieser zweite Flow funktioniert nicht – er sammelt oder erhält keinen Trigger. Und schließlich gibt der nächste einen Fehler aus mit der Meldung: Die Ausführung der Template-Aktion 'Apply_to_each_2' ist fehlgeschlagen: Das Ergebnis der Auswertung des 'foreach'-Ausdrucks '@outputs('Fetch_updates,_changes,_or_deletions_from_feature_layer')?['body\/items']' ist vom Typ 'Null'. Das Ergebnis muss ein gültiges Array sein. Irgenwelche Gedanken?

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

Power automate Fetch updates erstellt keine gültige Eingabe?

MonikaWheat88

Okay, ich versuche wirklich zu verstehen, warum einige meiner Flows funktionieren und andere nicht. Ich habe ein paar Flows, bei denen ich versuche, eine Nachricht in Teams zu posten, damit die PMs wissen, wann Daten gesammelt werden. <\/P>

Dieses erste Bild meines Workflows postet korrekt.<\/P>

<\/span><\/P>Dieser zweite Flow funktioniert nicht – er sammelt oder erhält keinen Trigger.<\/P><\/span><\/P>Und schließlich gibt der nächste einen Fehler aus mit der Meldung: Die Ausführung der Template-Aktion 'Apply_to_each_2' ist fehlgeschlagen: Das Ergebnis der Auswertung des 'foreach'-Ausdrucks '@outputs('Fetch_updates,_changes,_or_deletions_from_feature_layer')?['body\/items']' ist vom Typ 'Null'. Das Ergebnis muss ein gültiges Array sein.<\/P><\/span><\/P>Irgenwelche Gedanken? <\/P> <\/P>

Finde mehr Beiträge mit dem Tag

Accepted answers

All comments

Aymen_Farhat

I am having a similar issue. Are there any updates for the Fetch updates feature in Power Automate?

LeviCecil

I just tried switching to the old designer and got the exact same error

The execution of template action 'Apply_to_each_2' failed: the result of the evaluation of 'foreach' expression '@{triggerBody()}@{body('Fetch_updates,_changes,_or_deletions_from_feature_layer')?['items']}' is of type 'String'. The result must be a valid array.

DominicRobergeIADOT

Have you tried to run your flow by NOT using the new Designer? Last month at the ESRI Dev Summit it was strongly suggested to keep using the "old" designer.

It might not change anything for you, but it doesn't cost anything to try it.

LeviCecil

I'm having the exact same issue with this flow using Gmail. It's not getting past the first "apply to each" before I get the array vs string error.

Tiff

Hello @AnthonyLatini, is this workflow still working properly or are there any reported issues? I am using the ArcGIS connector for the first time and setting it up similarly to this post, except using Outlook email instead of Teams. For example, I have the flow set up as when record is updated -> apply to each fetch updates -> another apply to each send email.

It is not working where I test the flow and make a change to the layer, nothing triggers and the flow does not even trigger the first step (where record is updated).

NataliyaLys

@AnthonyLatini Thank you for the updates. I just checked all my flows from the weekend, and since the update on the Nov 30th, everything has been running as expected!!! Thank you again for fixing!

AnthonyLatini

Hi @NataliyaLys -

We have pushed an update (around that time yesterday) to the ArcGIS Connector in Power Automate to fix one of the two issues that have been reported in multiple areas (and thought it would be good to post in this thread). I will be making a larger post about this shortly for the whole board to see. 😀

When the Fetch updates action is called, it returns an empty response

This issue has been tested extensively and appears to be resolved. This issue has been deployed to production.

NOTE: The issue with empty arrays is still under investigation and has not been resolved in this push.

Please let me know if you have any questions or if you see any other additional unwanted behavior.

NataliyaLys

@AnthonyLatini

I don't want to get too excited, but I noticed that starting November 30th, around 11am - 12 pm ALL my flows started running successfully.

I believe that there has been update to AGO, is the last day or so. Does that have anything to do with this change?

And here is a screen shot from before Nov 30 (11am-12pm).

Thank you,

Nataliya

AnthonyLatini

@ssweat - Hi there! As mentioned in previous posts, we are working to resolve this issue. At the moment, there isn't an ETA, however, this is the top priority on the team to resolve issues surrounding Fetch Updates.

Thank you for your patience on this issue!

ssweat

Hi @AnthonyLatini ,

I am having a similar issue. Are there any updates for the Fetch updates feature in Power Automate?

Thanks!

AnthonyLatini

@ZacharyHart @MonikaWheat88 @NataliyaLys @LaraJuliussonUSFS @SarahRijneke
Hello to everyone in this thread! 😀

I am catching up on this and wanted to provide feedback. At the moment, there is a known issue with the Fetch updates, changes, or deletions action. In the issue, the changes that are captured can come back as [ ]. Meaning, there weren't any changes captured even though there might have been a new record created, updated, deleted.

Both @Pavel148 and I have been attempting to track this issue down and are working with the ArcGIS Online team to determine the best way to reliably reproduce the issue and the determine a fix. This issue does not appear to be stemming from Power Automate or the ArcGIS Connector inside of Power Automate, but rather from the layers themselves.

In my experience, when testing this issue, I was able to reliably reproduce it on one feature layer, but then not reproduce it in another.

As a note, everyone appears to have their flows set up properly and you are working through it in the correct manner.

Please sit tight with us as we work to resolve this issue. Thank you all for your patience!

ZacharyHart

@MonikaWheat88 Did you ever figure this out? I have spent a while diagnosing this here at the Esri forums as well as MS PowerAutomate forums. I'm not saying this your exact problem, but here's an observation I had. I had a flow working perfectly fine, I hadn't modified save for a few things in the message being put into the Teams channel.

The error is misleading (well at least in this case) as it lead me to believe that the input from the Fetch Updates step based on the same error you received:

The execution of template action 'Apply_to_each_2' failed: the result of the evaluation of 'foreach' expression '@{outputs('Fetch_updates,_changes,_or_deletions_from_feature_layer')?['body/items']}@{body('Fetch_updates,_changes,_or_deletions_from_feature_layer')}' is of type 'String'. The result must be a valid array.

So I went back to my Team channel and looked for the last valid response to make it through. I then attempted to reformat the message output in PA and then the flow suddenly started working again. I don't have an exact before and after but I cleaned some things up and added spaces between each insert parameter in the message. I also didn't change out any of the parameters, like i kept the same editor tracking fields I wanted to see in the message.

This is a complete mystery to me, and since looking at your screen shots, it appears what I have discovered may not help you at all. But there are numerous, unsolved posts about this!

This was a false positive. It now appears that there is no discernable correlation between success & failure.

@SarahRijneke I reviewed your post as well; i'm trying a mix of edits/updates: add new text to string field, modify text in a string field, change the attributed on a coded domain field etc. No pattern has arisen yet.

EDIT!: The same flow which I modified and had working fine immediately failed the second time using the exact same test (change to a record).

@AnthonyLatiniHave you seen this thread yet?

ZacharyHart

@NataliyaLys @LaraJuliussonUSFS

I'm having the exact same issue as well. The flow as built fresh today, working fine, and then suddenly started failing without warning.

NataliyaLys

I'm experiencing a similar issue. I have a number of flows set up in Power Automate. The flows are listening for feature updates, and when updates are made (and conditions are met) an email get sent and email status is updated.

However, I have been noticing that the flows not always work as expected. I can see that flow is being triggered, but the 'fetch updates' output is empty?

I was told that there is a bug, it doesn't apper to capture the first update that is made.

But in this specific case i have issue with subsequent updates just not being fetched randomly. At least I don't see any patterns. I also openned a ticket with ESRI to see if someone can assist.

Thank you,

Nataliya

LaraJuliussonUSFS

I am having the same issue with intermittent success of the Power Automate ArcGIS connector. I am running the same trigger and action as shown above and it works much of the time, but I sometimes receive the error The execution of template action 'Apply_to_each_2' failed: the result of the evaluation of 'foreach' expression '@outputs('Fetch_updates,_changes,_or_deletions_from_feature_layer')?['body/items']' is of type 'Null'. The result must be a valid array.

ESRI, can you help please!?

SarahRijneke

I'm also struggling to understand why some of my flows work and then stop working out of no where. My flow should trigger anytime a change is made to a feature service but I've noticed that it doesn't always run when an update is made. In my example below, someone added a bunch of new features to the assignments feature service on Aug. 30th but the flow didn't trigger at all that day.

Nimm an der Unterhaltung teil

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

Schnellzugriffe

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