Bad Request Error 400 On all flows Using Fetch updates, changes, or deletions from feature layer.

KylaCupp_SBY

I'm using Power Automate to run multiple flows and regularly getting a failed flow where I get a Bad Request Error 400 on a Fetch Updates, changes or deletions from feature. I tried increasing the number of retries but I don't think that is the issue here as it can't reach the service so it won't retry. If I manually resubmit it, the flow runs successfully. 

This issue seems to have started after the 2026.2 update but I know correlation is not causation 😅. I could get really into the weeds and build a companion flow but I feel like this is possibly a bug or something I should be able to fix within the original flows. Maybe there is a better way to approach this flow but it's essentially to check for changes in a field.

Any suggestions are appreciated! 

Thanks!

Akshay Harshe

 

It looks like this may be an intermittent issue. When you mentioned that you "tried increasing the number of retries," are you referring to the Retry Policy setting under the action's settings? If not, I'd recommend trying that first. You could also add a delay of around 30 seconds before the Fetch action to see if that improves reliability.

 

The "Sync replica internal error" is being returned by ArcGIS Online and it is unrelated to either the ArcGIS Connector or the 2026.2 update. This error indicates that something is failing internally within the service. Based on the details provided, it may be related to editor tracking, as the Extract Changes endpoint can sometimes return this error under those conditions.

In some cases, this is a temporary issue. Resubmitting the request generates a new call to the Extract Changes endpoint, which may succeed. As a troubleshooting step, you can copy the changesUrl returned by the webhook action, append a valid ArcGIS token, and invoke the REST endpoint directly. If the same error occurs there, it would further confirm that the issue originates from ArcGIS Online rather than the connector.

One resolution that has helped in similar cases is to disable editor tracking and then re-enable it. Please note that this approach can result in the loss of editing history, so it should be considered carefully.

At this point, I would recommend opening a support case with the ArcGIS Online team, specifically regarding the Feature Service Extract Changes endpoint. They should be able to investigate the underlying service-side failure.