Approval and waiting
Two steps pause the run. In both, the pause is durable: the run leaves memory, releases resources, and comes back on its own when it should.
Human approval
Pauses until someone approves or rejects.
| Field | Use |
|---|---|
| Title | What appears in the pending list. Accepts data from earlier steps |
| Summary | The context for whoever decides |
| Role that may approve | The minimum role required in the space |
| Specific people | Optional. Left blank, anyone with the role |
| Deadline | Optional. With no deadline, it waits indefinitely |
Produces: whether it was approved, who decided, and the comment.
What happens in each outcome
| Outcome | Effect |
|---|---|
| Approved | The step completes and the run continues |
| Rejected | The run ends as not approved |
| Deadline expired | The run ends as expired |
There is no second path for "rejected". The "was it approved?" output never reaches the following steps carrying a no — if you need to handle both outcomes differently, the correct design is a condition before the approval, not after.
Who decides
Anyone with the required role in the space sees the pending item and decides. The decision is single: a second attempt to decide the same approval is refused.
See Deciding approvals.
How long it can wait
Days, if needed. The run consumes no resources while waiting — and survives any platform restart.
Wait
Pauses for time, with no person involved.
| Mode | Use |
|---|---|
| For a duration | In seconds. It has to be shorter than the agent's timeout |
| Until a date and time | A fixed moment, or one from an earlier step |
Produces: when it resumed and how long it waited.
A moment already past is not an error: the step continues immediately.
The resume moment is decided once and stored. Without that, a one-hour wait would never end if the run were resumed every fifty minutes.
When to use each
| Situation | Step |
|---|---|
| A person has to sign off before continuing | Human approval |
| Waiting for an external system to finish processing | Wait |
| Giving time for a value to become available | Wait |
| Publishing something only after review | Human approval |
Next steps
Was this page helpful?
Report a problem on this pageDo not send passwords, keys, tokens, or customer data.