I have had some issues regarding Microsoft Flow and Survey 123. Essentially the Flow could not see the surveys. Recreating the connector to Survey 123 fixed the issue however it is a concern that this is the second time that we have seen issues and we only know the connector failed as we were testing, we cant go live with this without the ability to know when it fails.
If it fails there is no way of alerting us to an issue which means the first we will hear of it is when emails are not received on a survey being submitted. The concern is that the Flows could stop working due to a Survey 123 fault without warning.
Is anyone else having this issue or has anyone solved it successfully.
One of the most common reasons for the connector to break in MS Flow is the refresh token (the long-life token) has expired. Aside from deleting/creating the connection again, you can re-establish the connection by going to (left-hand menu) Data > Connections. You should see any connectors that have disconnected and have the opportunity to reconnect them.
Hi James, thanks but I don’t think this is the problem here.
Any more ideas ? This is really bugging me now !!
I checked again this morning and the Survey123 connector is still completely AWOL from Flow. Yesterday, I had to refresh my ArcGIS Online credentials for a test workflow I had set up about a month ago. After entering my credentials, the connector disappeared and is no longer shown in the list of connectors. It also does not come up in the results when I search for it. Is this an issue I need to raise with Esri tech support, or should I talk to my organization's point person for Office 365 and contact Microsoft tech support?
Our understanding is that this is an issue in MS Flow, so Microsoft would be the appropriate contact to raise a support issue with. We have also notified our contacts with MS Flow about this.
The connector was setup and able to see the surveys. After 2 days the Flows stopped running. I verified this based on the run time of the Flows and compared it the dates that surveys got submitted. There are no errors in Flow, it simply did not trigger. Unlike some of the other threads I am seeing on this issue I didn't have to recreate the connector however I did have to reauthenticate with the same Survey123 credentials. The connector was not in a disconnected state when I looked and in fact everything looked ok other than the surveys were not displaying. If I remember correctly the survey I have connected to was displaying an identifier number instead of the survey name.
Unlike Rogers issue below we never lost access to the Survey123 connector option. I am not experiencing any other issues like this with existing, non-Survey123, Flows. I don't think this is a token expiry issue given the short period of time between creation and the issue occurring (2 days). Additionally after fixing the last issue the Flow has been working consistently for the last 2 weeks.
The issue appears to be an authentication issue between Flow (opposed to the Microsoft tenant) and Survey123.
The Flow is currently in UAT and not been transferred to production over concerns that the system may not be suitable for use if it could fail without notice.