Docs

Runs

11 articles
  1. Runs · 3 min read

    Download a file a run kept

    Attachments, documents and form uploads that steps bring in are kept with the run. Download them from the step that brought them in.

  2. Runs · 3 min read

    Export run history, or download a run log

    Export CSV saves the runs your filters show as a spreadsheet file. Download the run log saves one whole run, every step, as JSON.

  3. Runs · 5 min read

    Find a run in run history

    Run history lists every run in the workspace, newest first. Narrow it by workflow, environment, outcome and period, and show or hide test runs.

  4. Runs · 5 min read

    Fix a failed run

    Open the failed run, read which step failed and why, fix the cause in the workflow or the service it uses, then run it again.

  5. Runs · 3 min read

    How long runs and their files are kept

    Each workflow keeps its most recent live runs — 10 on Free, 20 on Starter, 200 on Pro, all on Enterprise — and its last 20 test runs for 7 days. Files go with their run.

  6. Runs · 3 min read

    Make a step try again when it fails

    Set a step to try again up to 5 times, 5 to 60 seconds apart, before it fails the run — for services that are briefly down or busy.

  7. Runs · 6 min read

    Read a run: steps, inputs and outputs

    A run's page shows each step in order, what went into it, what came out, any console lines, the error where it stopped, and the variables it used.

  8. Runs · 3 min read

    Run a workflow again from a past run

    Run again starts a new run with the same input as a finished run, on the workflow's published version. Use it after you have fixed what made a run fail.

  9. Runs · 3 min read

    Stop a run

    Stop this run ends a run that is queued, running or waiting. It stops before its next step; a step already underway finishes.

  10. Runs · 4 min read

    What each run status means

    Queued, Running, Waiting, Succeeded, Failed, Stopped and Skipped — what each one means for a run, what counts towards your runs, and what each step's status means.

  11. Runs · 5 min read

    Why a run was skipped, not queued

    A skipped run never started — runs used up, a paid step on a free plan, or a workflow switched off, unpublished or deleted. Nothing waits to run later.

Still stuck? Ask us.

The assistant answers from these articles, and hands you to a person when one is free. Support hours are 9:00 to 19:00 IST, Monday to Friday; outside them, leave a message and we reply by email.

Chat with us