Solution for Timeout for Power Automate ArcGIS Connector with ArcGIS Online

[CScholer]

We are using Power Automate to create flows which are triggered by different Survey123 Apps. To connect a survey with a flow, we must create a connection and deposit the credentials of an AGOL user.

Every 2 weeks, this ArcGIS Connector in Power Automate is losing the login and the flow stops running. Our research showed that there might be a solution with ArcGIS API key and ArcGIS PaaS-Connector. https://doc.arcgis.com/en/microsoft-365/latest/power-automate/faqs.htm#anchor1

Unfortunately, it appears that there is only a solution for ArcGIS Enterprise and the use of ArcGIS API key to ensure the constant connection. And the ArcGIS PaaS-Connector seems not to work for feature services which we get from working with Survey123.

As we work with ArcGIS Online, we expect a solution for the AGOL environment as well. 

For our automatization, for which we use Power Automate and Survey123, it is crucial to have a continuous and steady connection. It is very time and cost consuming to check and refresh the connection for all flows every 2 weeks.

[SeanKMcGinnis]

Hello @CScholer - thank you for submitting the idea and I am sorry you are encountering this issue.

The token timeout issue for the ArcGIS for Power Automate Connector was resolved earlier this year, so I am surprised the you are encountering the issue. Are you working in a secured Azure Government tenant? If so, which one?

A couple points regarding the other connectors you referenced:

• There is a known limitation with the Survey123 connector where their refresh token is still timing out in two week intervals. The team have upgrade plans to address this issue in the coming year.
• The ArcGIS Platform connector does not have capabilities to access hosted feature services. Currently it only accesses the location services that are delivered by platform.

If you are having the timeout issues, I would suggest you submit a support ticket.

[gti_esri]

Hello @SeanKMcGinnis

I'm wondering if this issue is really solved?

On my side, as you can see on the picture below, power automate failed...

And the error message in Power automate

Thanks very much...

Geoffrey

[SeanKMcGinnis]

@gti_esri - What you are experiencing is an expected outcome when using the Survey123 connector. Updates were not made to the Survey123 connector for Power Automate. You will find the authentication capabilities operating as expected if you transition to the ArcGIS Connectors for Power Automate. The ArcGIS connectors now include the Survey123 trigger and actions and uses the updated connection management capabilities. The ArcGIS Connectors will keep the connection alive as long as it runs within the lifespan of the refresh token.

[gti_esri]

@SeanKMcGinnis: Thanks very much!

I will ask for a premium power automate account, then I will upgrade my power automate workflow.

Geoffrey - Esri BeLux

[DustinEdge_Boroondara]

@gti_esri Can I ask why you made the comment about the premium account? Will it help with the connections?

[gti_esri]

Hi @DustinEdge_Boroondara ,

My issue has been solved indeed with the premium account...

So I confirm it was the right solution

[DustinEdge_Boroondara]

Hi @gti_esri 

I also found this on another forum and seems to make more sense rather than "upgrade to premium account".

https://community.esri.com/t5/arcgis-for-power-automate-blog/quick-tip-keeping-the-arcgis-connectors...

[gti_esri]

Hi @DustinEdge_Boroondara ,

Indeed, your solution is an excellent workaround if the connection is not used by triggers or actions in other feeds.

This was not my case, and then the Premium solved it...

[SeanKMcGinnis]

@gti_esri  & @DustinEdge_Boroondara - the solution you are referencing are actually connected.

The Survey123 connector returns the 'refresh token' when the flow is created. By default an organization has the refresh token has a timeout of 14 days which is why users encountered the errors. The ArcGIS Connectors for Power Automate handle the management of refresh tokens as long as the connection is used within the life of the 'refresh token'. Moving to the Premium Account does not resolve the issue, but it does provide the enhanced connection management. The blog post shared is a way to make sure the connection is used within the appropriate time frame for you organization.