I have an issue with the ArcGIS Power Automate and the ArcGIS Online. I'm building my webhook, and it works fine for the first few days, then after that, the connection for some reason got broken, and I need to add it again and configure all my triggers and actions to read from it again... Is that a known issue?
How many days? I thought it had been updated to not time out in the new versions but the connection did use to time out every 14 days?
The last time it only worked for one day, then it timed out. From where could I check the time-out settings?
There's no real space for timeout settings, it's a back end setting on Esri's side, if it's happening every day it's probably a different issue and I'm not sure what could be causing it right now.
We are experience similar issues. Last week it was just the Fetch Updates action would completely stall. This week it still stalls but now our webhooks don't work either. It would be great if we could at least get an acknowledgement of these issues. We've been resorting to using the REST API via the HTTP action, which is blazing fast for querying and updating data, but to replicate a webhook looks to be quite complicated. See attached image.
I started getting this today too.
@AJD I am sorry to hear that. Is there any other information you can provide us to reproduce the issue. Authentication issues in ArcGIS for Power Automate are bit tricky to reproduce and in lot of the case the error it throws comes from Microsoft which is not useful.
Normally, ArcGIS Access and refresh token doesn't expire within that small of a time frame. Is your feature service gets overwritten with new data? Or are there any other restrictions on log in?
I have to add two of the same Enterprise 11.3 connections and toggle between them to be able to see any of my services in the trigger dropdowns.
To get around the OP’s issue, I also made a flow with a single ArcGIS trigger that runs once a week to keep the connections refreshed. I was told to do this at Dev Summit. It would be nice if ESRI would either fix this with Microsoft or let everyone know about this simple workaround to keep persistent connections.
@LeviCecil Unfortunately, this is as designed by Enterprise or Online. There is a validity on refresh token provided by ArcGIS Enterprise and Online so they will expire at some point. Having a flow that runs every certain time interval will ensures renewal of the refresh token.
You can find more information regarding types of token and their default and max values here Specify the maximum token expiration time—Portal for ArcGIS | Documentation for ArcGIS Enterprise. There is another post on how to create a recurring flow that might be helpful to some: Quick Tip: Keeping the ArcGIS Connectors for Power... - Esri Community.
We are also seeing random connection issues with the ArcGIS connector after not having any issues for months. Has anyone let ESRI tech support know about this?