Power Automate はさまざまなタスクの自動化を可能にします。しかし、一部のフローは毎日実行されるわけではなく、月に一度か二度しか実行されないこともあります。接続が他のフローのトリガーやアクションで使用されていない場合、実行頻度が低いことで問題が発生する可能性があります。新しいトークンを取得するためのリフレッシュトークンは2週間のみ有効です。私が接続を有効に保つために使っているヒントは、週に一度実行されるフローを作成し、フィーチャ レイヤーをクエリすることです。これにより接続が使用され、新しいリフレッシュトークンが取得され、タイムアウトを防ぎます。<\/P>
Doesn't matter what feature layer we use?
@SeanKMcGinnis Thank you for the helpful post! Do I need to do something similar for a Survey123 connection?*No need to answer my question. I swapped out my Survey123 triggers with the ArcGIS Connector trigger "When a survey response is submitted".
Thanks for the tip! I set mine up to have it email me when the flow runs so I know it ran successfully.
It should be noted, this flow requires a Premium subscription to use the "Get data from feature layer" action.
@NateHollenbeck Did swapping away from the Survey123 Connector to the ArcGIS Connector "When a survey response is submitted" work for you? This is an issue I've been battling with my Survey123 connectors every 13 days.
Thank you for this tip; however, I've found that my Survey123 connection needs refreshing after 14 days even if the flow successfully ran during that time. Would this trick help, or is there something else going on?
Hi @MelissaD1,
That's the mystery I'm trying to solve as well. It would be nice if the Survey123 Connector authentication issue could just be updated to allow for longer times, but it seems this issue has been ongoing for a while. Unfortunately, I created about 12 complex flows using the Survey123 Connector before becoming aware it was an ongoing issue.
@Mekeke - unfortunately, this tip will not work with the Survey123 Connector. That connector does not update the refresh token in the same way the ArcGIS Connectors for Power Automate and will always timeout when the token expires, which by default is 14 days.@WilliamW -The Survey 123 connector is no longer being maintained and all new capabilities will be included in the other ArcGIS connectors. The Survey123 Connector was ported over to the ArcGIS Connectors for Power Automate and that is where it was updated and the issue was addressed.
@SeanKMcGinnis Thank you for the response. I'll start replacing Survey123 Connectors on my flows with the ArcGIS Connectors.
Does this work for the ArcGIS Enterprise connectors as well?
Does the same logic apply to the "Get data from feature layer" for the ArcGIS Enterprise action?
That is, can you use this trick to keep ArcGIS Enterprise connections refreshed automatically?
Good Day @McKinneyPatrick_PA - yes it will.
Hi @SeanKMcGinnis ,
Thanks for the quick tip of OAuth token refresh mechanism. It helped to keep my connection active.
However, based on the February 2026 update, we understand that API Key authentication is now available, with tokens valid for up to one year. However, when creating a connection in Power Automate, it prompts only for the Enterprise URL, Client ID and does not provide an option to enter the API key. Am I missing anything, wanted to double check before I re-configure my production app? Thanks.
@NaginiAmancherla1 The documentation is ahead of the release for the PaaS Connector. We have handed off the 2026.1 release to Microsoft and they have only rolled out ArcGIS and Enterprise connector and not PaaS at the moment. Since we don't know when they will, the documentations usually released week after the final hand off to Microsoft.
サインインしたメンバーは投稿、更新のフォローなどができます。初めてですか？無料アカウントを登録してください。
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
