Completion Statuses Explained
What the badge on each submission is telling you
Each completion carries a status describing how far the submission got through the sequence. Most are Success. The others each point at a different kind of problem.
The five statuses
| Status | What it means | What to do |
|---|---|---|
| Success | The submission completed. The contact was created or updated, the answers were filed, and the configured actions ran. | Nothing. This is the normal state. |
| In progress | The submission was recorded and the rest of the sequence was still running when the status was last written. | Give it a moment and look again. A completion stuck here is worth reporting, since it suggests the sequence did not finish. |
| Failed | Something in the sequence did not complete. | Open the completion. The answers are intact, so you can act on the lead by hand while you investigate. |
| Error | An error was recorded against the submission. | Open the completion to see what was recorded. If a webhook was configured, the response from your endpoint is stored here too. |
| Abandoned | The submission did not reach a completed state. | Usually no action. Treat a pattern of these as a signal about the form rather than about any one person. |
Important: A status other than Success does not mean you lost the lead. The submission is recorded before any action runs, so the answers are safe. What failed is something downstream — a message, a webhook, an enrichment. Open the completion, read the answers, and follow up by hand if it matters.
What a completion stores
The answers
submitted data
required
Everything the person entered, including answers on fields you chose not to map to the CRM. This is the only place unmapped answers exist.
The contact
link
optional
The contact record the submission created or updated.
Uploaded files
attachments
optional
Any files submitted. These are also attached to the contact.
The booking
appointment detail
optional
Where the submission booked a meeting, its details are held with the completion.
The webhook result
response and error
optional
What your endpoint returned, and any error. The place to look when a webhook appears not to have arrived.
The assignment
member
optional
Which member the lead was assigned to, and on what basis.
Tip: A run of non-Success statuses that all began at the same time usually points at one shared cause — most often a webhook endpoint that went down. Check the timestamps before investigating each submission separately.
