Skip to main content
Manual checkpoint steps are planned and not yet available as a step type. The description below reflects the intended design for the step type. Manual checkpoints already exist today in Runbook mode — see Manual checkpoints in Runbooks.
A manual checkpoint step would pause a journey mid-execution and require a human to confirm or validate something before the run continues. This is different from a purely automated step — the journey would wait for a person to take an action (check something in a UI, verify a state, confirm a condition) and record the result.

​
Intended idea

As a step type, a manual checkpoint would work similarly to how checkpoints work in Runbook mode today: a human marks success or failure, optionally adds notes or attaches evidence, and the journey proceeds based on the outcome. This would make it possible to mix automated HTTP request steps with human-in-the-loop validation in a single journey — useful for workflows where some verification can’t (or shouldn’t) be automated.

​
Manual checkpoints today

If you need manual checkpoints now, use Runbook mode. Runbooks guide a support agent or operator through a journey step-by-step and support manual checkpoints natively. See Manual checkpoints in Runbooks for how they work today.