Read the right measure
Entries, form status and workflow executions answer different questions. A saved submission can have a failed follow-up action. A retry can create another workflow attempt without creating a new submission.
Open Reports/Analytics from the form or submissions workspace. Check the date range, selected form and any source filter before comparing totals.
Investigate a failed action
- Find the affected form and submission.
- Open its execution/attempt details.
- Read the failing node's status and sanitised error message.
- Correct the connection, mapping or destination.
- Use the supported Retry action if appropriate.
- Verify that a new attempt and its result appear in history.
Do not delete the original attempt to make the report look successful. If the destination may have received the request before a timeout, check it before retrying.
Protect operational data
Reports should expose counts and execution metadata to authorised users. Detailed answers and attachments belong in the protected entry view. Avoid putting API tokens, full private payloads or unnecessary personal values in script logs and error messages.
Verify changes
For a new integration, submit one successful QA entry and one deliberately rejected request to a controlled test destination. Confirm both outcomes in the appropriate workspace, then resolve or clearly label the test failure.
See Submissions, Workflows and Webhooks.