Runs and fixing failures
Every submission that starts a workflow creates a run. Open a workflow and choose Runs to see them, or open a response and expand Workflows. A run lists each step with its timing, its result and, when it failed, why.
Why a run fails
Section titled “Why a run fails”- A service didn’t answer: a rate limit, an outage, a slow webhook. Usually temporary.
- A connection stopped working: an expired login to Google or Slack, a revoked key. The run is parked on that step until the connection is repaired.
- The step is set up wrong: a wrong recipient, a deleted spreadsheet, an email with no body. Fixing it means editing the workflow and publishing.
- The step can’t work for this one response: the respondent left the email empty, or typed an address that bounces. The workflow is fine; this response isn’t.
Retry from here
Section titled “Retry from here”On the failed step, Retry from here runs it again and continues. Steps that already succeeded are never repeated. When the workflow has been published since the run started, you’re asked whether to retry with the original version or the latest one. Pick the latest when you fixed the step; a step you removed in the fix is skipped and the run continues from what followed it.
Release
Section titled “Release”A run parked on a broken connection shows Release instead. Repair the connection under Integrations, then release the run: the step runs for the first time, nothing is sent twice. When several runs are parked on the same connection, the Runs page shows a banner with Release all, which releases every run it was blocking.
Skip and continue
Section titled “Skip and continue”When a step can’t work for this response and that’s acceptable, Skip marks it skipped and runs the rest of the workflow. Nothing is repeated, and the step records who skipped it. A condition, route or approval can’t be skipped, since there is no outcome to continue from.
Cancel
Section titled “Cancel”Stops a run that is still going: one that is running, or parked on an approval, a timer or a broken connection. Reminders and escalations for a parked approval stop with it. A run that already failed has nothing left to stop, so it can’t be cancelled; leave it as it is, or skip the failed step to let the rest finish.
In bulk
Section titled “In bulk”The Runs page has checkboxes. Select the failed or parked runs and retry, release, skip or cancel them together. Runs that moved on in the meantime are left alone and counted in the result.