Power Automate flow returning empty reponse when using the 'Fetch Updates changes or deletions from feature layer

[narmour1979]

Hi

I've been going round in circles with this one for the last few days. I have a flow which was working fine up until about a week ago. It includes the 'fetch updates' action, which has started to return an empty response in the output, which basically causes the flow to bail (although reporting that it ran successfully).

The output looks like this:

This then creates issues for the connectors further on which rely on dynamic content from this action. 

This seems to only be occurring on the first edit made to a new point, subsequent edits are being picked up. This seems entirely in line with an issue that is discussed here: https://community.esri.com/t5/arcgis-for-power-automate-questions/flow-works-when-testing-but-doesn-... (second page of comments). In the comments there is no resolution, even though the discussion was about 18 months ago. 

Bizarrely, the flow was working flawlessly during the build phase of this app (up to February this year), then we had to down tools for a few months while a few changes were negotiated. When I resumed work a few weeks ago, the issues started. 

@AnthonyLatini you responded in the hyperlinked question about the issue with fetch updates not working on the first update made to a new point. Is there any movement on this? 

[TimLohnes1]

Any update. I have a similar, but not same issue. My When a record is created in a feature layer is not triggering. Been working for months. I saved as a new flow and the response and the new one triggers but returns no features. Much different response/output than a week ago. Feel like something in the connector just changed. I'll post a separate question, but thought I would check with you.

[narmour1979]

This is apparently related to a known bug which has been logged since 2023: 

https://support.esri.com/en-us/bug/the-fetch-updates-changes-or-deletions-from-feature-lay-bug-00015...

We escalated it and are waiting expectantly for the June release, which will drop sometime today. I'm the same as you though, mine worked flawlessly for months, then I had to recreate it and it was broken. 

[Tiff]

This is related to my case from last year! Sorry to hear you ran into a similar issue. I just met with someone from Esri support and this is still in product plan so she said maybe the next release...