Survey123 Webhook looses "Existing record edited" trigger

[JenniferMcKee__GISP]

Has anyone experienced issues with ArcGIS Survey123 hosted surveys loosing the "Existing record edited" trigger setting? We have at least 5 surveys that require this optional trigger event to be selected.

We have found that we loose the "Existing record edited" trigger setting when there are

• ArcGIS Online updates
• Survey123 updates published from Survey123 Connect to AGOL
• Power Automate Connector password update
• random occurrences that we cannot determine the source of

We do have a Microsoft Power Automate flow following a similar process as in this useful blog https://community.esri.com/t5/arcgis-for-power-automate-blog/quick-tip-keeping-the-arcgis-connectors... to keep our token refreshed but we have to update our Survey123 owner account password every 90 days. When this occurs we do pause flows temporarily to update this but we check the flows afterwards to ensure the surveys needing this trigger are set appropriately.

If anyone has tips or tricks for using a P.A. flow or notebook script to check webhook trigger settings I would LOVE to read about them and possibly use one that may work in our state GCC tenant.

[CherylWheeler11]

Hi Jennifer,

I actually reported a similar case last week, when exactly the same scenario happened to us. It affected weekend works on site and caused much disruption. 

Here is the link to my message. Let's hope that someone from ESRI can advise us of the root cause. So many factors involved that it is difficult to ascertain from our end.

I would appreciate it if you could update me if you hear anything back from ESRI or anybody else, and I will do the same.

Have a good day.

Cheryl