nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Timeout for Power Automate ArcGIS Connector

EendrulatGH

Microsoft's documentation for the ArcGIS Connector list a few limitations, including:

Connections will time out after 14 days and must be refreshed manually by initiating a sign-in to ArcGIS.

Does this mean that any PA flows using the connector will need to be manually updated every 2 weeks? Is there any longer term plans on the roadmap to address this, or suggested workarounds to avoid this manual step?

Appreciate any guidance!

Find more posts tagged with

Accepted answers

SeanKMcGinnis

Hi @EendrulatGH - your understanding is correct. The connection uses a token to connect to ArcGIS Online and it expires after 14 days forcing the user to refresh the connection.

We are working with Microsoft and investigating other methods for authenticating to avoid the two week expiration, but no timeline for release has been set.

SeanKMcGinnis

@PaulGiroux1& @Katrin_Hils - thanks for reaching out.

To answer your question regarding the token timeout, it is no longer an issue with the ArcGIS for Power Automate Connectors. We worked with Microsoft to adjust the way the refresh tokens were be refreshed and now there is no need to refresh the connection as long as the flow runs within your refresh token's lifespan.

The Survey123 Connector is different connector using the previous authentication method. There are plans to update the authentication process to alleviate the need to refresh the Survey123 connection every two weeks, but that is managed by another team.

All comments

SeanKMcGinnis

Hi @EendrulatGH - your understanding is correct. The connection uses a token to connect to ArcGIS Online and it expires after 14 days forcing the user to refresh the connection.

We are working with Microsoft and investigating other methods for authenticating to avoid the two week expiration, but no timeline for release has been set.

EendrulatGH

Thanks for the confirmation!

abul123

Hi @SeanKMcGinnis,

Is there any update on this?

Thank you!

RobertAnderson3

It's a 90 day time out now on the ArcGIS connector, I believe on all builds of it.

PaulGiroux1

@SeanKMcGinnis, you mentioned working on other methods to keep connections active. First, can you confirm what @RobertAnderson3 said about the 90 day time out? If that's correct, then I'm gold but if it's still 14 days, then I'll need to find other methods (API key, etc?).

I have a public Survey123 form so not sure the longest period before the form is used to report an issue so I want to make sure my flow it stays alive, regardless. We're also building flows with ArcGIS webhooks wanting to control this for those also.

Katrin_Hils

Hi Community,

we are struggling with the same issue. In our case we have over 10 Surveys (in AGOL) and at the moment around about 15-20 Power Automate flows connected to these surveys. It's quite a pain to check every 2 weeks whether the connection is still there. As there was an development for ArcGIS Connector in ArcGIS Enterprise, I was hoping the same for ArcGIS Online. Unfortunately, this is not the case for the moment.

Therefore, I posted the issue as an Esri Idea and wanted to share this post (https://community.esri.com/t5/arcgis-for-power-automate-ideas/solution-for-timeout-for-power-automate-arcgis/idi-p/1335303) with you. I guess it might help, if this post gets some Kudos.

I kindly want to ask you to please give Kudos to this Esri Idea. I guess the more Kudos, the better and the higher the priority? 🙂

Thank you!

SeanKMcGinnis

@PaulGiroux1& @Katrin_Hils - thanks for reaching out.

Kevin_MacLeod

@SeanKMcGinnis roger that, use the ArcGIS Connector.

However, it was noted at UC 2024 that even then; connections that only activate less than every two weeks will lose the token. You had a 'keep alive' script that would 'jiggle the handle' once every two weeks; to keep it alive. Would you kindly share that script or flow?

JoabelBarbieri

It seems auth expires from time to time and our flows just stop working. if you don't pay attention and reconnect, lots of business-critical workflows will just stop and you'll be left wondering what happened. These connectors should never expire.

SeanKMcGinnis

@JoabelBarbieri - we are sorry you are having issues with the connections. My suggestion is to submit an Esri support ticket so we can have people look into the source. When submitting the request, please provide details on the connectors you are using and the issue you are encountering? When you do submit an incident, please send me an email, including the ticket number, to smcginnis@esri.com and I will follow along with the case as the appropriate teams determine the source of the issue.

Tiff

Hello @SeanKMcGinnis, thank you for this information and for your recent responses on this thread! I am following up to see if there have been any updates on the 2 week timeout. I had spoken to some Esri staff in the past year or so. Also, is this the best thread to be following for updates, or is there another place that updates will be shared, specifically about the 2 week timeout authentication period? Thank you!

RobertAnderson3

Hi @Tiff the ArcGIS Connector (the orange one) no longer has an issue with tokens timing out, the Survey123 Connector (green one) does still have this two week timeout though (the trigger doesn't because it receives the token with the payload, but things like the Create report action will still have the 2 week timeout). Though I see below if the ArcGIS Connector flow isn't triggered in 2 weeks it will still timeout, but mine run consistently so I can't speak to that.

That said, it seems now the Survey123 Connector actions are all available in the ArcGIS Connector as well, so you could always move to that, however the ArcGIS Connector is part of the paid plan while the Survey123 Connector is not.

Tiff

Thanks @RobertAnderson3,, I actually mixed up this thread with my primary question, which was on the Survey123 connector. While I have access to the premium ArcGIS connector, there have been some problems with it and thus I would rather stick with Survey123 despite the 2 week timeout. I actually had no idea that the ArcGIS connector flow would time out. Is this unique to each flow or just the connection itself?

In addition, in reference to my initial question, do you happen to have the most recent/authoritative forum post for the Survey123 connector 2 week timeout issue? I searched and just cannot find it. I would like to keep up with updates. Thank you again!

bcaldwell

Going to chime in for 2025 - still have issues with the ArcGIS Connector timing out. Currently I'm pushing WKT geometry and attributes to AGO when a row is added or updated in a dataverse table. We had a lull in field data over weather, which also meant no updates to the dataverse table, so I'm assuming the connection still has to be jiggled every two weeks, unfortunately. I suppose its time to write a scheduled flow 😄

Dawtry

I am just going to post that I have recently started using PA with the ArcGIS connectors. It works great except for the two week timeouts. I am trying something I found here: https://www.cloudpointgeo.com/post/how-to-avoid-expired-tokens-for-arcgis-connectors-in-power-automate as something that just runs a dummy function on the token weekly. I am hoping this fixes my issue because I have noticed that some of my live links to fields get messed up when the the token fails and I have to re-add them and delete the old messed up ones, which is cumbersome to do every two weeks.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.