# Wait

Source: https://openflow.run/en/docs/nodes/wait/
Language: en
Product version: 0.1.0-beta.77

Suspend a branch and continue it manually or at a configured time.

Use Wait when a branch must pause while other ready work can continue. Continuation resumes the same Run and its fixed execution context.

## Prompt and context

Configure a prompt and bind named context inputs for the person or system that will continue the work.

```json
{
  "op": "node.add", "as": "review", "type": "wait", "name": "Wait for review",
  "prompt": "Continue after the draft has been reviewed.",
  "inputs": { "draft": { "kind": "value", "value": "A proposed customer reply" } }
}
```

Use the `pending` path for notification work and `continue` for the work that must remain blocked. Connect each path explicitly.

Wait suspends this branch until a continuation is accepted; the same Run then returns its result.

**Input**
Start the workflow, then continue the pending Wait.

**Expected result**
{"message":"Review finished"}

**Before running**
An Open Flow deployment is needed to execute or import this example. The preview itself runs offline.

[Download workflow](https://openflow.run/docs/examples/wait-and-resume.openflow.json)

## Outputs and decisions

`pending` exposes prompt, context inputs, expiry, and available action URLs. `continue` exposes the accepted action, resolution time, comment, and context inputs. Bind these objects only on paths where they exist.

The deployment persists the Wait before releasing its notification branch. The first accepted continuation wins; repeated submissions do not resume it again. Public action URLs are scoped bearer capabilities, so do not expose them in ordinary public logs.

## Automatic continuation

Wait optionally accepts static timing configuration:

```json
{
  "op": "node.update", "node": "WAIT_NODE_REFERENCE",
  "set": { "config": { "autoContinue": { "kind": "after", "durationMs": 3600000 } } }
}
```

Use `kind: "at"` with an explicit-offset timestamp for an absolute time. Relative timing starts at each Wait registration. Manual continuation remains available, and the first accepted continuation still wins. Server requires scheduled continuation before its seven-day expiry.

Clear `config.autoContinue` explicitly for manual-only waiting. Approval does not support this timing option. Wait has no ordinary Task retry or `onError` policy.

## Sources

*   [docs/authoring/node-authoring.md](https://github.com/oomol-lab/open-flow/blob/e25a738d170322734572a0b8a1323cb00b9d355a/docs/authoring/node-authoring.md#wait-automatic-continuation)
*   [docs/control/contracts/control-api.md](https://github.com/oomol-lab/open-flow/blob/e25a738d170322734572a0b8a1323cb00b9d355a/docs/control/contracts/control-api.md#9-public-wait-action-hook)
*   [docs/control/contracts/control-api.md](https://github.com/oomol-lab/open-flow/blob/e25a738d170322734572a0b8a1323cb00b9d355a/docs/control/contracts/control-api.md#wait-automatic-continuation)
*   [packages/open-flow/src/workbench/browser/runtime/editor/addNodeOptions.ts](https://github.com/oomol-lab/open-flow/blob/e25a738d170322734572a0b8a1323cb00b9d355a/packages/open-flow/src/workbench/browser/runtime/editor/addNodeOptions.ts)