Submissions
What gets recorded when someone submits, and how to read the action log.
A Form Submission is a submitted — or draft — response. It records what was answered, which config version it was answered against, and what happened next.
What is on the record
- Status —
Draft,Submitted,Processing,Sent, orError. - Response Payload — the answers.
- Form and Form Config — the form and the exact config version used.
- Anonymous — whether the visitor was logged in.
- Submit Action Result — a per-action log of how the submit actions were processed.
- Retry Count — how many times processing has been retried.
- Any uploaded files, attached to the record like any other Salesforce file.
Reading Submit Action Result
This is the field to open when something did not happen. It is a JSON log with one entry per submit action, each carrying:
status—Completed,Skipped,Error, orPendingoutput— anything the action produced, such as a created record's Iderror— the failure message, when it failed
Skipped is not a failure: it means the action had an Only run when… condition that did not match.
Status, in order
A healthy submission moves Submitted → Processing → Sent.
Error means at least one submit action failed. The answers are safe — the submission record exists
with its payload regardless of whether the actions succeeded. Only the follow-up work failed.
Retrying
An administrator can open a failed submission and click Retry Submit Actions. Processing re-runs
from the first action that has not completed — actions already Completed are not repeated, so a
retry will not create a duplicate record for a step that already worked.
Fix the cause first: the purpose whitelist, the flow, or the target data. See Submissions and errors.
Who can see them
Marketeers cannot. Analysts can read them. Only administrators can edit or retry. See Getting access.
