Skip to main content

Documentation Index

Fetch the complete documentation index at: https://hypha-docs.plinqx.app/llms.txt

Use this file to discover all available pages before exploring further.

The WAIT node pauses flow execution for a specified duration, useful for rate limiting, delays, or waiting for external conditions.

​
Overview

WAIT nodes enable:
  • Delays: Add delays between operations
  • Rate Limiting: Space out API calls to respect rate limits
  • Polling: Wait before retrying operations
  • Timing Control: Control execution timing

​
Configuration

​
Duration

Set wait duration:
  • Value: Numeric duration value
  • Unit: Milliseconds (ms), seconds (s), minutes (m), hours (h)
  • Minimum: 0 (no wait)
  • Maximum: No hard limit (but consider flow timeout)

​
Examples

  • 1 second: 1 with unit s
  • 5 minutes: 5 with unit m
  • 500 milliseconds: 500 with unit ms
  • 1 hour: 1 with unit h

​
Use Cases

​
Rate Limiting

Add delays between API calls to respect rate limits: 
ACTION: Call API
WAIT: 1 second
ACTION: Call API again

​
Polling

Wait before checking status: 
ACTION: Check status
WAIT: 5 seconds
ACTION: Check status again

​
Delayed Processing

Add delays for timing-sensitive operations: 
ACTION: Create resource
WAIT: 2 seconds
ACTION: Verify resource

​
Output

WAIT node provides output: 
{
  "requestedDurationMs": 1000,
  "actualDurationMs": 1001,
  "startedAt": "2024-01-15T10:30:00Z",
  "completedAt": "2024-01-15T10:30:01Z"
}

​
Best Practices

Consider Timeout

Account for wait time in flow timeout

Use Sparingly

Minimize wait times for better performance

Document Purpose

Document why wait is needed

Test Timing

Test wait durations in different scenarios

​
Next Steps

ACTION Node

Add delays between actions

TRY Node

Retry with delays