TL;DR
Pausing stops new runs; in-flight runs finish (or freeze, your choice). Scheduled triggers skip while paused. Resume picks up new triggers immediately — missed triggers during the pause don't replay by default.
Pause behavior
Toggle Paused: new triggers are ignored, in-flight runs complete by default (or freeze mid-step with the "hard pause" option — rare, for incident response).
What happens to missed events
Events during a pause don't queue — a lead that arrived while the speed-to-lead workflow was paused won't be processed on resume. The Missed Triggers view lists them for manual replay if needed.
Scheduled runs
Scheduled triggers skip silently while paused and resume on the next scheduled occurrence — no catch-up storm.
Pause vs disable vs archive
- Pause — temporary, everything preserved, one toggle back.
- Disable — same but signals "not coming back soon" in the UI.
- Archive — retired, removed from the active list, restorable from archive for reference.
Did this answer your question?
