Agiled Docs

Delay nodes pause workflow execution before the next step runs.

Use delays when the next action should happen later, not immediately after the trigger. Examples include follow-up reminders, waiting for a customer response, post-meeting check-ins, renewal reminders, or internal review periods.

Use a condition after long delays when the record may have changed. For example, check that an invoice is still unpaid before sending a reminder.

Delay vs Schedule

Use a delay when the workflow has already started and should wait before the next step. Use a scheduled workflow when the whole automation should start at a known time or recurring cadence.

For example, use a delay after an invoice is sent to wait three days before a reminder. Use a scheduled workflow to review overdue invoices every weekday.

If the timing is customer-facing, name the delay clearly so reviewers understand why the automation waits before sending a message, creating a task, or updating a record.

Add A Delay

Open the workflow builder.
Add a Delay node from flow control.
Choose a duration in seconds or enter an exact resume timestamp.
Connect the next step after the delay.
Save and test the workflow.

Use delays for follow-up reminders, waiting periods, and scheduled handoffs.

Duration Delays

Use Duration (seconds) for relative waits. For example:

3600 waits one hour.
86400 waits one day.
604800 waits one week.

Duration must be zero or greater. Use a realistic test duration while building, then change it to the production duration before publishing.

Do not publish with a short test delay unless that is the real business timing. Test values can create reminders or follow-ups much sooner than intended.

Exact Resume Time

Use Until when the workflow should resume at a specific timestamp. The field expects an ISO timestamp, such as 2026-02-03T10:30:00Z.

Use exact timestamps for workflows tied to a known event time. Use a duration for simple relative follow-up timing.

Where to Place Delays

Place the delay after the step that creates the need to wait. For example:

After a proposal is sent, wait before creating a follow-up task.
After a form submission, wait before sending a second reminder.
After a ticket is closed, wait before sending an internal quality check.

Do not place a delay before required validation steps. If the workflow is missing a customer, owner, or related record, fix that before the delay.

Time Zones And Business Hours

Exact resume times use the timestamp you enter. Check the time zone before using an exact timestamp for a customer-facing email, appointment follow-up, renewal notice, or billing reminder.

If your process depends on business hours, add a review condition or task rather than assuming a delay will resume during working time. A duration delay can resume overnight, on weekends, or during holidays.

Check Run Detail

When a run is waiting, the run detail can show when the delayed step is scheduled to continue.

If a delayed run does not continue when expected, open the run detail and check the delay node, the scheduled resume time, and the next connected node. If the next action is invalid, the run may resume and then fail at that action.

If you edit a workflow while runs are already delayed, review existing waiting runs before assuming they will follow the newest version exactly.

Troubleshooting Delays

If a run waits too long, check the configured duration, exact resume timestamp, workflow status, and whether the run is still attached to an older workflow version.

If a run resumes too early, look for a short test value that was accidentally left in production. Also check whether multiple workflow versions or duplicate triggers created more than one run for the same record.

If the next step fails after the delay, fix the failed action instead of changing the delay first. The delay may have worked correctly, but the record may no longer meet the next step's requirements.

Add Delays