Error de Solicitud Incorrecta 400 en todos los flujos usando Fetch updates, changes, or deletions from feature layer.

KylaCupp_SBY

Estoy usando Power Automate para ejecutar múltiples flujos y regularmente obtengo un flujo fallido donde recibo un Error de Solicitud Incorrecta 400 en un Fetch Updates, changes or deletions from feature. Intenté aumentar el número de reintentos pero no creo que ese sea el problema aquí ya que no puede alcanzar el servicio, por lo que no reintentará. Si lo vuelvo a enviar manualmente, el flujo se ejecuta con éxito. <\/P>

Este problema parece haber comenzado después de la actualización 2026.2 pero sé que correlación no es causalidad 😅<\/span>. Podría profundizar mucho y construir un flujo complementario pero siento que esto posiblemente sea un error o algo que debería poder arreglar dentro de los flujos originales. Tal vez haya una mejor manera de abordar este flujo pero esencialmente es para verificar cambios en un campo.<\/P>¡Cualquier sugerencia es apreciada! <\/P>¡Gracias!<\/P><\/span><\/span><\/P>

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.