Webhook missing more submissions (Power Automate)

Question

In one of my most popular forms, which sees a several hundred submissions per day, I've been getting more reports of webhooks missing submissions (Power Automate). Any Esri response?

There is nothing wrong with the form or webhook. And most of the submissions are getting caught it seems. I am wondering if the webhook is being over-saturated now?

I have a flow which I abandoned a while back for security reasons, but may pick it back up. The idea was to watch the Feature Layer and grab new submissions directly from there. I dropped that idea after I released the layer needed to be visible to the public to allow for Power Automate to change variables in the FL (this needs to remain a public layer). I'll probably try creating a view layer this time since there is more urgency to get this working now.

SpatialCadet · Answer

Encountering the same issue, around 2-5% of webhooks failing to be received with Survey123, hard to diagnose when payload is not received no error log/identifier i can rely on to re-trigger report creation.

Any advice, response from ESRI would be greatly appreciate, appreciate error rate is low but depending on scale/number of submissions it can create project issues when information is project critical and users need to be informed.

JTessier · Answer

Thanks @DavidPike , yeah your last question mark is the nut of the portal webhook issue: it would be great if they would either fail gracefully and not just deactivate.  Again need documentation that talks about if they will try to self heal and try again later if they go inactive (or enhancement that allows for this AND for them to be purposely (manually) set to inactive), how many attempts are made and non-200s are accepted before they go inactive, and where they are stored (assuming portal webhooks are in the portal pgsql dbs) but not sure about the others.

DavidPike · Answer

@JTessier you may find that the NotificationStatus method on the webhook will show some timeouts around the time it becomes inactive.  A cause for us was the server the payload was being sent to not replying with 200s in time or if at all.  This then likely caused the webhook to fall over/(fail gracefully?)