WhatsApp Flow Lifecycle – Complete Overview
What Is a WhatsApp Flow?
A WhatsApp Flow is an interactive, structured user experience inside WhatsApp that allows businesses to collect inputs, guide users through forms, and complete actions such as sign-ups, bookings, or lead capture.
Every WhatsApp Flow follows a defined lifecycle, governed by Meta, to ensure consistency, reliability, and compliance.
Lifecycle Stages of a WhatsApp Flow
1. Draft
This is the initial state when a flow is created.
The flow can be edited, tested, previewed, or deleted.
Draft flows cannot be sent to real users.
Key points:
Unlimited edits allowed
Safe testing phase
Only stage where deletion is allowed
2. Published
The flow is live and available for end users.
Once published, the structure becomes locked.
Key points:
Flow can be triggered via WhatsApp messages
No structural edits allowed
Cannot be deleted once published
3. Deprecated
Used to retire a published flow.
The flow is permanently disabled for new users.
Key points:
Deprecated flows cannot be published again
This action is irreversible
Existing users may still see past interactions, but no new sessions can start
4. Throttled (System-Controlled)
Applied automatically by Meta due to quality or policy issues.
Message delivery or usage may be limited.
Key points:
Not user-initiated
Indicates potential compliance or performance concerns
May be resolved automatically or require corrective action
5. Blocked (System-Controlled)
The flow is fully restricted by Meta.
Key points:
Flow cannot be used or sent
Typically due to policy violations
Requires resolution via Meta guidelines or support
Important Lifecycle Rules
Only Draft flows can be deleted
Published flows cannot be edited or deleted
Deprecation is permanent and cannot be undone
A deprecated flow can never be re-published
System states (Throttled/Blocked) are controlled by Meta, not users
Why Deprecate a WhatsApp Flow?
Deprecation is used when:
A flow is outdated or replaced by a new version
The flow has incorrect logic or content
You want to stop usage without breaking past data
Meta requires retirement for compliance reasons
Best Practices
Finalize and thoroughly test flows before publishing
Clone a published flow if changes are needed
Use clear naming conventions for versions
Deprecate only when you are certain the flow is no longer required
Summary
Understanding the WhatsApp Flow lifecycle helps you:
Build compliant, scalable experiences
Avoid irreversible mistakes
Maintain clean and controlled user journeys
Managing flows correctly ensures better performance, user trust, and long-term stability.