Ligantic
Knowledge Base
Tutorials
Updates
Search Articles
Login
Free Sign Up
Home
Get Started
Tutorials
How-to guides
Reference
Explanation
Spaces
Schemas
Flows
Experiences
Endpoints
SDK and CLI
Browse documentation
Home
Get Started
Spaces
Schemas
Flows
Experiences
Endpoints
SDK and CLI
Docs
/

Control - Wait

Type identifier: control:wait Category: Control Operations

Description

Delays the run for a specified number of seconds. The wait duration can be set as a static value or dynamically via an input handle.

Input Handles

Handle

Data Type

Required

Description

trigger

trigger

Yes

Execution trigger input

seconds

number

No*

Wait duration (*only if dynamic mode)

Input Handle Details

seconds

  • Type: number
  • Notes:

    • Only present when seconds configuration is set to "dynamic"
    • Value is in seconds (can be decimal for sub-second waits)
    • Must be a valid number

Output Handles

Handle

Data Type

Description

done

trigger

Triggered after the wait completes

Configuration Options

Property

Type

Required

Default

Description

label

string

Yes

"Control Wait"

Display label for the node

seconds

Literal number or dynamic

Yes

{ type: "literal", value: 1 }

Wait duration in seconds

Configuration Details

seconds

  • Type: { type: "literal", value: number } or { type: "dynamic" }
  • Notes:

    • { type: "literal", value: <number> }: Static wait duration
    • { type: "dynamic" }: Wait duration provided via input handle
    • Value is in seconds (for example, 0.5 for 500ms, 60 for 1 minute)
    • In Studio with v2 execution enabled, static waits use a forward-only duration editor without a direction toggle. A week is 7 days, a month is 30 days, and a year is 360 days; a day is 24 hours. The saved value and dynamic input remain numeric seconds.
    • V2 durations must be between 0 and 360 days, inclusive (31,104,000 seconds). Empty, negative, and longer durations show a validation error in the editor.

Behaviour

Execution Flow

  1. Node receives trigger on the trigger input handle
  2. Resolves the wait duration:

    • If literal: uses configured seconds.value
    • If dynamic: reads from seconds input handle
  3. Validates the duration
  4. Pauses the run for the specified duration
  5. Triggers the done output handle

For runs using the v2 engine, seconds must be a finite, non-negative number no greater than 31,104,000 (360 days), whether configured statically or supplied dynamically. The v1 engine's existing editor and duration behavior are unchanged.

Long Waits

A v2 run may enter the Waiting state during a long wait and resume when the wait ends. While it is waiting, the Flow Run page shows when the run will resume, with a live countdown. Child runs started by Flow - Execute show the same resume time as the top-level run they wait with. Each wait is limited to 360 days. Some runs require retained run data and have a 360-day resume deadline, measured from the first wait that requires that retention. Later waits do not extend the deadline. Runs already waiting keep their previously assigned resume deadline.

If a wait would end after that deadline, the run fails before entering Waiting, with a message identifying the parked value retention period. Shorten the wait or schedule a separate Flow run. Runs that do not require retained run data have no cumulative retention-based wait limit, but each wait is still limited to 360 days.

Wrapped secrets from Secret - Get are not retained as plain text while a run is waiting. Nodes that use them after the wait, such as Secret - Unwrap and Integration - SMTP, read the secret again from the secret store, so they receive its current value. Values with the Sensitive trait keep that trait after the wait. A plain-text value produced before the wait, such as the output of Secret - Unwrap, is retained with the run data until the run resumes; unwrap secrets after the wait when possible.

Success Path

After the wait duration elapses:

  • Output handle done is triggered
  • The run continues to connected nodes

Error Path

When validation fails:

  • The node fails when a dynamic duration is not a finite, non-negative number within 360 days
  • A literal duration outside this range is not accepted by the v2 engine

Edge Cases

Scenario

Behaviour

seconds is 0

Proceeds as soon as the run can continue

seconds is negative

Rejected by the v2 engine; v1 behavior is unchanged

seconds is not number

The node fails

seconds exceeds 360 days

Rejected by the v2 engine; v1 behavior is unchanged

Decimal values

Supported (for example, 0.5 = 500ms)

Examples

Static Wait Duration

{
  "type": "control:wait",
  "data": {
    "label": "Wait 5 seconds",
    "seconds": {
      "type": "literal",
      "value": 5
    }
  }
}

Input Handles:

  • trigger (trigger)

Output Handles:

  • done (trigger)

Dynamic Wait Duration

{
  "type": "control:wait",
  "data": {
    "label": "Wait (dynamic)",
    "seconds": {
      "type": "dynamic"
    }
  }
}

Input Handles:

  • trigger (trigger)
  • seconds (number)

Output Handles:

  • done (trigger)

Usage Pattern - Rate Limiting

[API Call 1] → [control:wait (1 second)] → [API Call 2] → [control:wait (1 second)] → ...

Usage Pattern - Polling with Delay

[Check Status] → control:if
                     ├─ if (complete) → [Process Result]
                     └─ else → [control:wait (5 seconds)] → [Check Status]

Related pages

Control - If
Conditional branching node that evaluates a boolean condition and directs the run down one of two paths. Supports both control flow mode (branching the run) and data mode (selecting between values).
Page not found. It may have moved or may not be published.
Browse documentation