Every run has its own page that shows what happened, step by step: what each step received, what it produced, and where and why it stopped. Open it when a run failed, or when you want to check what a workflow actually did.

Who can do this

Everyone in the workspace — Admin, Editor and Viewer — can read a run. Only Admins and Editors see Stop this run and Run again on it.

Steps

  1. Select Runs in the bar at the top of the page, then select the run's workflow name, or Open on its row. See Find a run in run history.
    • A notification that a workflow failed has View run, which opens the same page.
  2. Read the heading. It has the workflow's name with a Production or Development pill, and under it either Run 4,812 · published v4 for a live run, or Test run · draft v5 for a test.
  3. Read the facts row under the heading: Status, Started (to the second, with your time zone — 17 Sep 2026, 09:00:02 IST), Duration, Trigger, and Steps — how many succeeded of how many ran, such as 4 of 5.
  4. If the run failed, read the red banner: Step 3, Create invoice, failed. It says whether the steps before it completed — The two steps before it completed and their work stands. — followed by the error.
    • Select Jump to the failure to open that step and scroll to it.
  5. Look at the strip of step names under the facts. Each name is coloured by how that step ended, in the order the steps ran.
  6. Under Steps, select a step's name to open it. The failed step is already open.
    • Select Expand all to open every step at once.
    • Select the name again to close it.
  7. In an open step, read:
    • Input — the step's settings after the values from earlier steps were filled in.
    • Output — what the step produced. One item shows as one object; several show as a list.
    • Console — lines a code step wrote while it ran. It shows only when there are some.
    • The error in red, if the step failed.
    • Went down the Yes path, or Went down the Sales and Everything else paths, for a step that splits the run into paths.
    • A list step shows what it found or changed in the list instead of a console. See See what a list step did in a run.
    • Files the step brought in, with Download beside each. See Download a file a run kept.
  8. To copy an input or output, select Copy beside Input or Output. A toast says Copied — It is on your clipboard.
  9. If the run used variables, read Variables used at the bottom: each $vars. name, where it came from (Global or Workflow) and the value the run read. The last line, $env, says production or development.

What happens next

A run that is still going — Queued, Running or Waiting — updates itself on the page every two seconds until it ends, so you can leave the page open and watch it. Steps it has not reached yet are listed after the others, still, marked Queued. Nothing you do on this page changes the run, except Stop this run and Run again.

Good to know

  • What each step's time says: 1.4s when it finished; running while it runs; Retry 2 of 3 or retrying while it is trying again after a failure; Waiting · resumes in 1 d 23 h at a Wait step; skipped for a step marked to be skipped.
  • A step marked to be skipped shows Marked to be skipped., and what came into it went on to the next step unchanged.
  • A step set to carry on after a failure still shows as failed, with Carried on, as this step is set to. after its error, and the run goes on.
  • A pinned step in a test run shows { "pinned": true } as its input: the test used the pinned data instead of running the step.
  • Big outputs are cut. An input or output over 256 KB keeps only its start, with the note Over 256 KB — only the start is kept. Files on it can still be downloaded.
  • Variables used are recorded as they were when the run started. Editing a variable afterwards does not change what a finished run says it used. A variable with no value shows No value in Production (or Development). A Connection variable shows the connection's name, or A connection that was removed.
  • A step's error is kept to 2,000 characters; anything longer ends in ….
  • Download the run log at the top right of Steps saves the whole run as a JSON file. See Export run history, or download a run log.
  • Open the workflow at the top right takes you to the designer.

If something goes wrong

What you see Why What to do
That run is not here — History keeps the most recent runs of each workflow; older ones go. It may also belong to another workspace. The run was removed because newer runs replaced it, its workflow was deleted, or it belongs to a workspace other than the one you are in. Switch to the workspace the run belongs to. If it was removed, it cannot be brought back. Select Run history to go back.
Not copied — The browser would not allow it. Select the text and copy it instead. Your browser blocked access to the clipboard. Select the text in the box and copy it with your keyboard.
A step shows It did not finish. The run ended — it was stopped or ran out of time — while that step was underway. Read the run's own message at the top. See Fix a failed run.
Something went wrong inside this step, not in your settings. We have been told. The step failed for a reason on our side. Run it again later. If it keeps happening, raise a ticket and attach the run log.