Every run shows its status as a coloured dot and a word, on run history and on the run's own page. This is what each one means, and what you can do about it.

Who can do this

Everyone in the workspace can see run statuses.

Steps

  1. Select Runs in the bar at the top of the page. Each run's status is in the Outcome column.
  2. To see only runs with one status, choose it in Any outcome. See Find a run in run history.
  3. Open a run to see its status under Status, with the reason when it did not succeed.

What happens next

Run statuses

Status What it means Counts towards your monthly runs
Queued The run is recorded and waiting for its turn to start, normally within a few seconds. Not yet
Running Steps are running now. The run's page updates every two seconds. When it finishes
Waiting The run is paused at a Wait step and picks up on its own at the time shown, or when what it waits for arrives. It is not stuck. Not while it waits
Succeeded Every step that was reached finished. Yes
Failed A step failed and was set to stop the run, or the run could not go on. The run's page opens on the failed step and says why. Yes
Stopped Someone selected Stop this run, or Bizomate stopped a test run after 5 minutes. No
Skipped The run never started: the company's runs were used up, the plan does not include a step it needs, or the workflow was switched off, unpublished or deleted before its turn came. Nothing ran. No

Step statuses

Inside a run, each step has its own status, shown by its colour and by the words beside it:

What it shows What it means
A time, such as 1.4s The step finished.
running The step is running now.
Retry 2 of 3, or retrying The step failed and is set to try again; it is waiting before its next try.
Waiting · resumes in 1 d 23 h, or waiting A Wait step is holding the run.
skipped The step is marked to be skipped; what came into it went on unchanged.
Queued The run has not reached this step yet. A path the run may not take is still listed until it gets there.
— with Needs a paid plan The run was skipped for the plan, and this is a step that needs a paid plan.

Good to know

  • Test runs never count towards your monthly runs, whatever their status. They are limited to 50 a day per workspace on Free and 500 a day on paid plans instead.
  • Failed runs tell people. When a live run fails, each Admin and Editor of the workspace gets a notification — Weekly sales summary failed — with the error and View run. When the next run of that workflow succeeds, they get Weekly sales summary is running again.
  • Skipped is not a failure. Nothing went wrong in the workflow, and a skipped run is not tried again later. See Why a run was skipped, not queued.
  • The Workflows page shows the last run of each workflow that succeeded or failed; stopped and skipped runs do not change it.

If something goes wrong

What you see Why What to do
A run stays Queued for minutes The run could not be picked up. Open it; if nothing changes, stop it and select Run again. If it keeps happening, raise a ticket.
The run stopped unexpectedly several times and was given up. We have been told. The run failed three times for a reason on our side. Select Run again. If it happens again, raise a ticket and attach the run log.
A run is Waiting longer than you expected Its Wait step is set to wait that long, or what it waits for has not arrived. Open the run: it says when it picks up. Stop it if it is no longer needed.