Hi,
Last weekend 3rd/4th May 2025 a very odd thing happened in that many of our surveys were updated without our doing. The updated times were random for each survey and this resulted in the webhook setting being changed so that the 'Existing record edited' was turned off and an older version of a csv being used for a select from file question.
We have the 'Require update to the latest version of this survey' turned on so all users were forced to update and then unable to continue.
We cannot work out what has caused this and it affected our site workers for the weekend.
I wonder if anybody else has experienced such issues?
From what I can see, there are three possible culprits :-
I would appreciate any comments on how we can avoid future occurrences of similar behaviour. I was looking at the below setting but not sure which is best to choose. (However, this may be a totally irrelevant setting??)
Thanks for any feedback.
Have a good day!
We're experiencing a similar issue with unprompted updates as well.
Users for one of our surveys were prompted to update their field app survey with an update that we never pushed. Now we're experiencing an issue where submissions from that survey form are generating duplicate notifications through Make.com. Though in our case the webhook hasn't been changed to disallow editing as yours has.
Any update from the Survey123 dev team on this so far? I wouldn't be surprised if the issue is linked to the bad backend update that got pushed out earlier this month and caused issues with the web app version last week.
Interesting Marc. Yes, would be good to hear from ESRI