Update: 12/1/2023 - BUG-000163195 The 'Fetch updates, changes, or deletions from feature layer' action sends back empty responses
An issue was reported in a few threads on the forums related to fetching updates after a trigger was initialized and having it return an empty response. This could cause any actions after this to fail since the subsequent actions are waiting for information to passed through (which was not happening).
We have pushed an update to the ArcGIS Connector in Power Automate to fix this issue.
This issue has been tested extensively and appears to be resolved. This fix has been deployed to production.
NOTE: The issue with empty arrays is still under investigation and has not been resolved in this push.
Before fix:
Note that the response is empty, but the "handshake" between Power Automate and ArcGIS Online was successful.
After fix:
Here is the same layer, but with the correct response and information.
Food Analogy:
I was thinking of a good way to describe what is happening in the action and came up with a clever way to think about it.
Scenario 1: empty response
Scenario 2: empty array
Imagine you go to your favorite restaurant and order your favorite dish. You place your order with the server, and they say it'll be a 2 to 15-minute wait before the food shows up.
In the first scenario (the one that was fixed in this push), the server places the order, hears a bell that tells them table 42 is ready, heads to the kitchen for pickup, and then comes back to your table empty handed.
In the second scenario (the empty array scenario that we are still investigating), the server places the order, hears a bell that tells them table 42 is ready, heads to the kitchen for pickup, and then comes back to your table with an empty plate.
As always, please let us know if this specific issue is still occurring for you and your flows. 😄