Stop a pipeline to halt its run that's in progress. This article explains what happens when you stop a run, how long it takes, and how selecting Stop is different from turning a pipeline off.
What happens when you stop a run
To stop a run, open the pipeline in the designer and select Stop.
When you select Stop, the pipeline finishes the step that's currently running, then stops before it starts the next step. It doesn't cancel a step that's already in progress.
Stopping isn't always instant. Depending on what the pipeline is doing, a stop can take up to several minutes. For example, when a step is running a large query, a bulk operation, or a call to another service, the pipeline lets that finish first. If the pipeline is looping over many records, a few more records may finish before it stops. While the pipeline is stopping, it shows messages to let you know the stop is in progress.
When the run stops, it appears in the activity log as Stopped manually.
Stop vs. turning a pipeline off
Stop affects only the run in progress. It doesn't turn the pipeline off. Webhooks, schedules, and pollers stay active, so the next trigger event can start a new run. It also doesn't undo completed work. Steps that already ran, such as records created, emails sent, or files written, aren't reversed.
To stop a pipeline from running at all, turn it off. Use Stop to halt the run in progress, and the On / Off toggle to stop new runs from starting.
Stop and different pipeline types
Stop works the same way for every pipeline—it halts the runs that are active now. What differs is what can start a new run afterward:
Manual (runs when someone selects a button)—nothing starts on its own. The pipeline runs again only when someone starts it manually.
Starts with a trigger step—new trigger events can start new runs.
Scheduled—the next scheduled time starts a new run.
Polling—the poller keeps checking and can start new runs.
If a pipeline has more than one run active, Stop signals all of them.