Make the token for Survey123 valid indefinitely for Microsoft Power Automate Flows that use the Survey123 connector

[Jamie_Leitch_CNF]

Currently with a Microsoft Power automate (MSPA) flow that uses a connector for ArcGIS Survey123, the security token for the connector seems to only be valid for 30 days.  After this time, the flow will fail due to an invalid token with the error:

{

  "error": {

    "message": "Missing required parameters: \"token\"",

    "code": "001"

  },

  "success": false

}

Because the main reason for using a MSPA flow is to automate certain tasks, it would be ideal if this token would be valid either indefinitely, or for a much longer period of time, for example 1 year.  When the token lapses, there seems to be only one way to get the connection to work again and that is this:

https://community.esri.com/t5/arcgis-survey123-questions/changes-to-survey123-connector-in-power-aut... 

[SeanKMcGinnis]

@RobertAnderson3  - there will be no impact to the flows currently using the Survey123 connector. But in order to take advantage of the refresh token management, it will require flows to be updated to use triggers/actions in the ArcGIS for Microsoft 365 connector.

[NourSalamJMT]

@SeanKMcGinnis thank you for this timely information! How would this impact a custom PowerAutomate connector I have created for Survey123 in ArcGIS Enterprise? Would the team's work fix the issue there as well or does the fix only apply to ArcGIS Online? Thanks!

[ARyanWADNR]

@ChelseaRozekI haven't seen any issues with integromat and tokens. It is also a lot easier to reauthorize survey123 and other apps on there than it is in Power Automate IMHO.

[jrosacker]

@SeanKMcGinnis - commenting to see if you know whether this has been implemented, and if there are any development trackers or documentation I can refer to in order to see update status.

Thanks!

[MeganEngel]

Any update on this idea?  I have enabled a token refresh flow.  However, still encountering issues within my automated flows where they seem to forget all the input params from S123, and the only way to fix it is adding a new token.

This is NOT a viable solution when we rely on PowerAutomate for automated email and report generation for external clients.  I.e. we cannot always be going in there to fix this and re-run the automation so they receive their documents.

[ISP_graynic]

@MeganEngel switching our connection from Survey123 to the ArcGIS connector solved this for us. All the Survey123 triggers and actions are in the ArcGIS and ArcGIS Enterprise connectors. Once we switched from Survey123 to ArcGIS, we no longer had issues with our tokens needing refreshed. 

[MeganEngel]

@ISP_graynic , great thanks for the info! We really are not the biggest fans of the S123 connector, so will see switching to the ArcGIS connector.  If it not triggered for a few weeks will it 'forget' those input parameters like the S123 connector, because that is what S123 seems like it has issues with?

[ISP_graynic]

@MeganEngel we switched over from the Survey123 connector about 3 months ago and haven't had any issues since. According to the post below, it doesn't look like the token refresh is an issue at all with this connector. 

https://community.esri.com/t5/arcgis-survey123-questions/power-automate-survey123-connectors/td-p/15...

[Jamie_Leitch_CNF]

I have created a flow in MS Power Automate that simply gets all surveys owned by me using the S123 connector, and this flow runs daily.  When it runs it refreshes the token, so it is always renewed.  This seems to have solved the issue