BUILDING AUTOMATIONS
Follow-ups and limits
Understand drafts, active states, expiry, run caps, and the messaging window.
Understand the automation state
A published flow cannot be changed back into a draft. Drafts cannot be enabled directly from the automation table. Expired or exhausted flows need their limits edited before they can be enabled again.
- Draft: unfinished work; reopen and publish it before it can run.
- Active: the flow is enabled, subject to connection, matching, and limits.
- Off: a published flow that is disabled.
- Expired: its automatic-expiry period has ended.
- Limit reached: the configured maximum triggers has been reached.
- Delivery error: inspect the execution details before taking action.
Automatic expiry and run caps
Automatic expiry defaults to 48 hours and can be configured from 1 to 48 hours. Its clock starts at publication; drafts do not expire.
The maximum-trigger cap belongs to the automation and is shared across recipients. Accepted executions count toward the cap, including executions with failed sends. It is not a per-person allowance.
One delayed follow-up
You can configure one delayed follow-up after the response sequence. The current editor offers a delay of 1–23 hours. The follow-up must still fall within the 24-hour window from the recipient’s latest interaction.
A newer recipient interaction cancels the pending follow-up. A disabled, deleted, or expired flow, or a closed messaging window, also prevents sending.
Keep your workflow within platform rules
Keep replies relevant to the recipient’s interaction and respect requests to stop. Reflect is not designed for unsolicited bulk DMs, unlimited follow-ups, or bypassing Instagram restrictions. Automated flows do not use the Human Agent extension.