Submissions and errors
Review what came in, diagnose a failed submission, and retry it safely.
Reviewing submissions
- Open the Form Submissions tab.
- Filter by Status — for example
Error. - Review Response Payload, Request Message, and Submit Action Result.
Analysts have read-only access here. Marketeers have none. Only administrators can edit or retry.
Reading Submit Action Result
This is the field that tells you what actually happened. It is a JSON log with one entry per submit action:
status—Completed,Skipped,ErrororPendingoutput— anything the action produced, such as a created record's Iderror— the failure message
Skipped is not a failure. It means the action had an Only run when… condition that did not
match.
The answers are safe
A submission in Error still has its Response Payload. The visitor's answers were recorded; only the
follow-up actions failed. You are never recovering lost data — you are re-running work.
Retrying
After fixing the cause — a purpose whitelist, a flow, or the target data:
- Open the failed Form Submission record.
- Click Retry Submit Actions.
- Watch Status move to
Processing, thenSenton success orErrorif it still fails.
Retry resumes from the first action that has not completed. Actions already Completed are not
repeated, so a retry will not duplicate a record that was already created. Retry Count increments
each time.
Requires the Administrator role.
Diagnosing common failures
error mentions |
Likely cause |
|---|---|
| Field-level access, or a field name | The purpose no longer grants edit access to that field, or the field changed. |
| A required field on the target object | The action does not map a field the object requires. Add it. |
| A flow, or a flow variable | The flow changed after it was whitelisted. Refresh it in the Purpose Manager to re-read its variables. |
| A validation rule or trigger | Something else in the org rejected the write. Fix that, then retry. |
| A field holding a single value, with the answers listed | A checkbox group is mapped onto a field that stores one value. Point the mapping at a multi-select picklist field, or limit the question to one answer. |
| A field is not a multi-select picklist, so its write mode cannot be append | The mapping's Write mode is set to Add to existing on a field that holds one value. Only a multi-select picklist can be added to; set the row back to Overwrite. |
| An unknown field write mode | The action's stored write mode is neither overwrite nor append. Re-open the mapping row and pick a Write mode again. |
Order of steps matters
If an action needs the Id of a record created earlier, the two must be in separate steps — each step runs as one transaction segment, in order. An All or nothing step rolls back entirely if one of its actions fails, so a partially-successful step leaves nothing behind. See Submission actions.
