Survey123 Keeps Creating Records

[ZachBodenner]

Hello,

I had a weird thing happen with a Survey123 submission: I'm testing out a a survey and when I hit the submit button, the icon just sat there and spun for an unusually long time. I went into the hosted layer data tab and found that over 10,000 records had been created. the submission was still spinning and when I refreshed the data tab on the hosted layer, I found that the count was still going up!

Letting the survey submit for about a minute resulted in 20k records. It wasn't a one-off, I tested again and the same thing happened. 

I had previously constructed this survey for a referenced feature service where it behaved as expected. I created a hosted layer and basically copied the construction of the survey from the referenced to the hosted .xlsx.

Has anyone ever seen this before? 

[jcarlson]

Oh man, a blast from the past. This happened to us once, too. I don't remember how the issue was resolved, though... Do you see anything helpful in the Network tab of your browser's developer tools? (Assuming you are submitting from the web form.)

[ZachBodenner]

Yeah, just a rapid succession of applyEdits:

[abureaux]

Oh wow. Haven't seen this yet. Curious what the resolution will be though.

[ClayDonaldsonSWCA]

Something bizarre is going on with webforms with geopoints. Getting thousands of requests like you are showing. But only if a geopoint question is present. Not an issue in the field app either.

[ZachBodenner]

That seems like S123's bread and butter. I'm surprised there aren't so many more people reporting it. I think I'll go ahead and log an ESRI ticket and keep this thread updated.

[RobertAnderson3]

Not something I have ever encountered, granted I virtually never use webforms, I just tested one of the web forms with a geopoint we do have but did not encounter this (it is a form from published with 3.12 so it's old anyways, and inactive)

I am definitely curious to hear what's happening with this though, keep us posted!

[ZachBodenner · Accepted solution]

Solution achieved:

I hadn't yet gone into the settings for the layer to enable editor tracking. After I did that the issue stopped. Weird thing is that I had published a separate test layer, also not done that, and had no issues. ESRI tech support suspects it was a "glitch," for whatever that's worth.

[CoryBowlin]

Thanks for posting this. I had a similar experience. Our issues were multiplied in thousands of unintentional added features. Turning that on fixed it.