> ## Documentation Index
> Fetch the complete documentation index at: https://fliqr.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Pause a Flow with delays
> Use the Delay block to wait seconds to days between steps, and know when to use drip campaigns instead.
The **Delay** block pauses the current Flow for a set duration, then continues to the next block for that contact.
## When to use Delay
* Space out onboarding tips inside one Flow
* Wait briefly before a follow-up question
* Give a human time to join before a reminder message
## Configure a Delay
Place it between the message you just sent and the next step.
Choose a value in seconds, minutes, hours, or days (per the picker in your workspace).
Wire Delay → next Message / Action. Publish and test with a short duration first.
## Delay vs drip campaign
| | In-Flow **Delay** | [Drip campaign](/docs/core-concepts/flows/drip-campaigns) |
| ------------ | ------------------------------ | ---------------------------------------------------- |
| Scope | Continues the same Flow run | Sends a scheduled series of Flows over time |
| Best for | Short waits inside one script | Nurture sequences across hours/days |
| Subscription | Implicit (contact is mid-Flow) | Explicit subscribe / unsubscribe actions |
If you need a multi-day nurture with easy unsubscribe, use a drip campaign. Use Delay for short pauses inside a single conversation script.
## Caveats
* Channel messaging windows still apply (for example Meta’s 24-hour rules). A Delay that lands outside the window may require a template or opt-in message type.
* Long delays make debugging harder — name the Flow clearly and log key fields before the wait.
* Publishing a new Flow version can affect contacts waiting on a Delay; see [Test and publish](/docs/core-concepts/flows/test-and-publish).
## Next
Schedule a series of Flows over time.
Timing and publish discipline.