On October 21 and 22, some webhook endpoints received submissions that were weeks or months old, in some cases going back to December 2025. Some of these were incomplete submissions: forms a visitor started but never sent (when this was enabled for the form). They arrived with partial or empty answers and a response number of 0, because incomplete submissions never get a number.

We're sorry for the trouble this caused, especially if it set off emails or automations, or created duplicate records on your side.

Why it happened

We retry webhooks that fail. Some older submissions, including incomplete ones, were still marked as "not delivered". Until now, a flaw in the retry process meant it rarely reached them. While building the new webhook event log, we made the retry process more reliable. As a result, it worked through all of those older submissions at once and sent them to the connected endpoints.

The affected responses also show October 21 as their "Completed" date in the responses list, because marking them as delivered changed that date. Failed webhooks are only retried within 24 hours of the submission, and at most 3 times. Their answers were not changed.

What we changed

• Incomplete submissions are never sent. Only forms that were actually submitted trigger a webhook.
• Retries have a time limit. Failed webhooks are only retried within 24 hours of the submission, and at most 3 times.
• Old submissions are never sent automatically. Anything older than 24 hours is no longer delivered on its own, even if you connect a new endpoint to the form.
• No more duplicate sends. Two retry runs can no longer overlap, and the automatic process never sends a submission twice to the same endpoint.
• "Completed" dates stay unchanged. Marking a response as delivered no longer changes the date shown in your responses list.

You can still resend any event yourself from the webhook event log under Settings → Notifications / Connections → View events. Every webhook sent in the last 30 days is listed there, including the ones from this incident.