When designing workflows in Microsoft Power Automate, timing plays a crucial role. Whether you're managing approvals, scheduling notifications, or controlling the pace of a process, the Delay and Delay Until actions provide powerful ways to pause and resume flow execution.

While both actions serve a similar purpose, choosing the right one can improve performance, reliability, and overall workflow efficiency. Understanding when and how to use each action is essential for building effective automation solutions.

Understanding the Actions

Delay

The Delay action pauses a flow for a specified duration, such as seconds, minutes, hours, or days, before continuing to the next step.

This action is ideal when you need a simple, fixed waiting period within an active workflow.

Delay Until

The Delay Until action suspends a flow until a specific date and time is reached.

Instead of waiting for a set duration, the flow resumes execution at an exact timestamp, making it suitable for scheduled or deadline-driven processes.

When to Use Each Action

Use Delay When:

• A short pause is needed between workflow steps.

• External systems require time to process or synchronize data.

• You want to prevent actions from executing too quickly in succession.

• A fixed waiting period is sufficient for the business process.

Use Delay Until When:

• Actions must run at a specific date and time.

• Tasks need to be scheduled for future execution.

• Workflows are tied to deadlines or business schedules.

• Notifications or reminders should be sent during designated business hours.

Practical Scenario: Approval Reminder System

One common business use case is managing approval requests.

Workflow Example

1. A request is submitted.

2. The flow starts a Delay action (for example, 2 hours).

3. The approval status is checked.

4. If the request is still pending, a reminder notification is sent to the approver.

For more advanced scheduling, you can replace Delay with Delay Until by calculating a future timestamp, such as the next business day at 9:00 AM.

This approach ensures reminders are delivered during working hours rather than at arbitrary times.

Best Practices

To make the most of these actions:

• Keep delays as short as possible to maintain workflow responsiveness.

• Avoid using delays inside large loops or high-volume processes, as this can impact performance.

• Use dynamic expressions such as addHours(utcNow(), 2) or formatDateTime() when configuring Delay Until.

• Combine delays with conditions to create intelligent, decision-based workflows.

• Always account for time zones when working with scheduled executions and date calculations.

Key Takeaways

Although both actions pause workflow execution, they serve different purposes:

• Delay pauses a flow for a specified duration.

• Delay Until pauses a flow until a specific date and time.

By selecting the appropriate action for your scenario, you can build workflows that are more reliable, efficient, and aligned with business requirements. Proper use of these actions helps ensure processes run at the right time while maintaining system performance and stability.