Skip to main content

Wait Node

🎯 Purpose​

Delays workflow execution for a specified duration. This allows for throttling and synchronization before continuing to the next node.

📥 Inputs​

  • Duration — A numeric value indicating how long to wait.

  • Unit — A dropdown selection specifying the time scale:

    • Milliseconds
    • Seconds
    • Minutes

📤 Outputs​

  • Passes on its input to the next node after waiting the specified amound of time. No data is transformed or generated. The output simply continues workflow execution after the pause.

📘 Best Practices​

  • Use Short Delays When Testing: Long waits can make debugging slower.
  • Avoid Unnecessary Pauses: Only insert waits where timing control is required.
  • Combine With External Checks: Use the Wait Node before polling APIs or checking for file availability.

🧪 Test Cases​

  • Given: Duration Value = 500, Time Unit = milliseconds Expected: Workflow resumes after 0.5 seconds.
  • Given: Duration Value = 5, Time Unit = seconds Expected: Workflow resumes after 5 seconds.
  • Given: Duration Value = 1, Time Unit = minutes Expected: Workflow resumes after 60 seconds.
  • Given: Invalid or negative duration Expected: Error: invalid wait duration

🗂️ Real-World Use Cases​

  • Rate Limiting: Prevent exceeding API rate limits between requests.
  • Synchronization: Ensure external services complete actions before the next node runs.
  • Timed Triggers: Delay execution to align with scheduled processes or intervals.

✅ Step-by-Step (Quick Start)​

  1. Add Wait Node to your workflow.
  2. Enter a numeric value in Duration.
  3. Select a time unit from the Unit dropdown.
  4. Connect the Wait Node to the next step in your workflow.
  5. Run the workflow and verify that it resumes after the specified duration.
  6. Save and deploy.