Wait

Pause for a number of seconds, then pass the records through unchanged.

When to use it

Pause for the configured duration and pass records through unchanged. The wait still sits within execution limits. It is not a substitute for a durable external completion check.

Add and configure

Add Wait from the workflow step picker.
Give the step a recognisable name and connect its required inputs.
Set the options below. Nested names identify fields within an object or a list item.
Validate the recipe, inspect the test result, then run it on the intended data.

The step identifier used in the editor’s code view is wait.

Settings

Setting	Accepted value	Required	Default	What it controls
Seconds (`seconds`)	number; maximum 3600; greater than 0.0	Yes	Not specified	How long to suspend before the next step runs. The runner's `timeout_seconds` still applies — set it to at least `seconds` plus a small buffer.

Inputs and outputs

Direction	Port	Content	Required	Multiple records
Inputs	`in`	records	Yes	Yes
Outputs	`out`	records	Yes	Yes

Effects, testing, and recovery

Transforms or passes records without a declared external side effect.

The declared preview behaviour is to execute this step. Reads, processing, or model usage can therefore be real. Read dry runs before using a preview with live connections.

No duplicate-prevention key is declared for this step. The step declares safe replay for its supported recovery path.

Example: Pause briefly between two steps

Step settings:

{
  "seconds": 0.01
}

Input records:

[
  {
    "id": 1
  },
  {
    "id": 2
  }
]

Expected output for this example:

[
  {
    "id": 1
  },
  {
    "id": 2
  }
]

Check the result

Inspect the selected run’s status, counts, errors, and output records. An empty collection can be a valid result, and a completed step can contain per-record failures where the step defines that behaviour. Check the next step’s expected record shape before publishing or delivering the result.