All connections stopped authenticating although they say they are connected - will not let us Switch Account

Question

Seems like at about 2pm all of our connections stopped working.  They all return unauthorized and will not let us Switch Account.  If I create a new connection it seems to work but we have dozens of flows and it is not realistic to update with new connections.

CalvinHarmin · Answer

This may only be relevant to users who utilize power environment 'solutions':

I did a different method that I would recommend for others that use power environment 'solutions' with many flows that all use the same connection reference, rather than going to each flow and changing the connection reference for each action.

Instead of creating a new connection reference in each flow, create a new connection at the power environment level. Then, update the connection reference at the solution level to point to the new (duplicate) connection. That way, if you have many flows using the same solution connection reference, you only have to update it in that one place, which is one of the benefits of connections and references when using solutions.

TLongSUGF · Answer

Since the update (and after we updated hundreds of connections) I have I identified two instances where data was submitted, and the survey123 trigger was completely bypassed.  This seems to be completely random as I have had them copy and resend and the second entry was successful.

I am concerned that this will continue and cause us to rethink ArcGIS connectors.  Unfortunately, we have no way of knowing until the customer contacts us.

Akshay Harshe · Answer

@TL2 We are investigating this right now.  We have added API key Authentication to the ArcGIS Connector with the latest release. We had consulted MS before this update and didn't experience this issue in our testing where old flows in our QA connector were working as expected. We are not sure why the the token should expire on existing connections which are currently working. I also see that MS doesn't also show the Reconnect button or switch account in the connections that are broken. We have setup a meeting with the MS to further investigate this.

For now you can do following steps which are unfortunately is painstaking if you have lot of flows.

* Open any of the flow that is not working. 
* Select an ArcGIS Action.
* Click Change connection
* Click Add New
* Use ArcGIS Online User Credentials and give it a reasonable name.
* Sign in.
* Update all the ArcGIS actions and triggers to use the newly created connections.
* If other flows are using the same connections then update all the actions and triggers to use the newly created connection and save the flow.
* For Triggers/Webhooks, confirm that the webhook is working and active on your Feature service.

Hope this helps. Apologies for the inconvenience.