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!

[Tiff]

Hi @SeanKMcGinnis, I had NO idea that it would no longer be fixed. Last I heard the Esri team was working with Microsoft on the 2 week timeout, but that it was difficult.

Thank you for your interest in learning more about my experiences. I didn't see your post initially, but I sent a response in to Robert above. If you are curious, I have cases/bugs open with technical support (related bugs also noted). - BUG-000169874,  BUG-000163136, BUG-000159797, BUG-000168340

I'm also open to connecting further offline. 

[SeanKMcGinnis]

Hi @Tiff - if you send me an email at smcginnis@esri.com, we can set up a time to talk. I look forward to hearing more about what you are encountering.

[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-automat...) 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 · Accepted solution]

@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.

[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.