• Instructions to Ask a Question

    For any assistance, please click the "Ask a Question" button and select the Pabbly product for which you require support.

    We offer seven comprehensive applications designed to help you efficiently manage and grow your business:

    Our support team endeavors to respond within 24 business hours (Monday to Friday, 10:00 AM to 6:00 PM IST). We appreciate your understanding and patience.

  • Due to Holi celebrations, our team will have limited availability. While we’ll continue to monitor threads, responses may be slightly delayed. Normal operations will resume on Thursday, 5th March 2026.

Delay (Pabbly)

Status
Not open for further replies.

Delay (Pabbly)​


Overview​

The Delay Module in Pabbly Connect allows you to pause workflow execution for a specified period before proceeding to subsequent steps. This powerful feature helps control the timing of your automated processes.

Delay Types​

1. Delay For​

1745318346135.png

  • Purpose: Sets a specific duration to pause the workflow.
  • Configuration:
    • Select a delay unit (Minutes, Hours, Days, or Weeks)
    • Enter a numerical value (e.g., 11)
  • Example use case: Wait 11 minutes before sending a follow-up email.

2. Delay Until​

1745318436616.png

  • Purpose: Pauses the workflow until a specific date and time.
  • Configuration:
    • Enter a date and time in YYYY-MM-DD HH:mm:ss format
    • Must be in UTC+0 Time Zone
  • Example use case: Schedule a promotional message to be sent at a precise future date/time.

3. Delay After Queue​

1745318480670.png

  • Purpose: Adds a waiting period after the last queued delay, helping control rate-limiting and race conditions.
  • Configuration:
    • Select a delay unit (Minutes, Hours, Days, or Weeks)
    • Enter a numerical value (e.g., 11)
  • Example use case: When multiple webhooks arrive in quick succession (like form submissions), using an 11-minute delay ensures each submission is processed separately. If a webhook with name="John" arrives at 3:00 PM and another with name="Sarah" arrives at 3:05 PM, the system processes John's data at 3:11 PM and Sarah's data at 3:22 PM, preventing system overload while maintaining a consistent processing queue.


 
Last edited by a moderator:
Status
Not open for further replies.
Top