Executing & Run History
One Execute click runs every step in order, waiting for each to finish before starting the next. This page covers what happens while a Pipeline runs, how to read the run-history list afterward, and exactly what the Cancel button does — and doesn't do.
Clicking Execute
From the builder screen (or the search screen — see Searching Pipelines), click Execute. This starts a new run and takes you to that run's status view.
How a Run Plays Out, Step by Step
A Pipeline run is strictly sequential — it never runs two steps at the same time. For each step, in order:
Step starts
│
▼
Pipeline waits for the step to reach a finished state
│
├── Step finishes successfully ─────────────────▶ move on to the next step
│
└── Step fails, or doesn't finish within
the Pipeline's "how long to wait per step"
setting (then it's treated as failed too)
│
▼
That step's On-Failure Behavior decides what happens next:
Stop → Pipeline run ends here, remaining steps never start
Continue → move on to the next step anyway
Skip → mark this step Skipped, move on to the next stepIf a step doesn't finish within the Pipeline's configured wait time (set when the Pipeline was created — see Creating a Pipeline), the Pipeline treats it exactly like a failure and applies that step's On-Failure Behavior. This is what the wait-time setting is for: without it, one hung step could keep a Pipeline "running" forever.
Once every step has either finished, been skipped, or the run stopped early on a Stop-behavior failure, the run reaches a final status — Completed, Failed, or Cancelled.
The Run-History List
Every Execute click is recorded as a run. The run-history list, shown on the Pipeline's own screen, gives you the full record: Status, Started At, and Completed At for each run. Click a run to expand it into a per-step breakdown — the status of each individual step (including whether it timed out) and a link through to that step's own execution detail, the same execution view you'd see if you'd run that Template on its own.
| Run Status | Meaning |
|---|---|
| Running | Currently in progress — one step is executing or the Pipeline is between steps. |
| Completed | Every step finished, whether successfully, skipped, or continued-past — the run reached the end of the list. |
| Failed | A step failed and its On-Failure Behavior was Stop, ending the run early. |
| Cancelled | You clicked Cancel and the run stopped after finishing whatever step was in flight at the time. |
The Cancel Button
While a run's status is Running, a Cancel button is available. It's worth being precise about what it does, because it isn't an instant kill switch:
In practice this means Cancel is best thought of as "don't start anything else," not "stop right now." If Step 2 of a five-step Pipeline is mid-flight when you click Cancel, Step 2 still finishes (or fails) on its own, and Steps 3 through 5 simply never run.