Delay — Input & Output

Output Ports

Port	Condition	Description
success	Delay elapsed normally	The configured duration has passed, or the target datetime has been reached. The workflow continues along this port. For in-process delays, the thread resumes. For durable delays, the workflow is reloaded from the persisted state and continues.
cancelled	Delay was cancelled externally before it elapsed	An external signal (via the BizFirst cancellation API) cancelled the pending delay. The workflow continues along this port, allowing the designer to handle early cancellation gracefully — e.g., skip the delayed step, log the cancellation, or take alternative action.
waiting	Durable suspend initiated	Fires immediately when the delay is persisted to the durable execution store (i.e., when the delay exceeds the `in_process_threshold_ms`). Connect a notification node here to alert an operator that the workflow is in a waiting state. This port is not mutually exclusive with success — both fire (waiting fires first, success fires when the delay expires).
error	Invalid configuration or persistence failure	Fires if the resolved `duration_ms` is negative, the `until_utc` string is not a valid ISO datetime, or the durable execution store fails to persist the workflow state. Details in `output.NodeName.error`.

Field	Port	Type	Description
`resumed_at`	success	string (ISO 8601)	The UTC datetime when the delay actually elapsed and the workflow resumed.
`planned_until`	success, waiting	string (ISO 8601)	The UTC datetime when the delay was scheduled to expire.
`actual_duration_ms`	success	integer	The actual number of milliseconds elapsed (may differ slightly from the configured duration for in-process delays due to scheduling overhead).
`cancelled_at`	cancelled	string (ISO 8601)	The UTC datetime when the cancellation signal was received.

{
  "resumed_at":        "2026-05-24T10:34:12Z",
  "planned_until":     "2026-05-24T10:34:00Z",
  "actual_duration_ms": 86412034
}