WhatsApp
WhatsApp Flows
Manage WhatsApp Flows status and lifecycle

Manage Flow status and lifecycle


After creation, WhatsApp Flows can be edited, published, deprecated, or blocked based on their state and performance. This page outlines how flow status works and how to manage it.



Flow lifecycle

WhatsApp Flows can transition through several statuses during their lifecycle. These statuses determine how the flow can be used and whether it is available for customers.

StatusDescription
DraftA flow enters the Draft state when it is first created or edited, and is available only for testing purposes.

Draft flows can be deleted if no longer needed. However, a published flow cannot be reverted to a draft.
PublishedWhen a flow is ready to send, you can move it to the Published state. In order to maintain consistency, published flows cannot be modified or deleted. If changes are required, you must create a new flow based on the original. A published Flow can transition to Deprecated or Throttled status, based on system monitoring or user decisions.

Deprecate a flow if it is no longer needed or must be removed.
DeprecatedDeprecated flows can no longer be sent to users but may still exist on their devices. You may still receive responses from those flows.
ThrottledWhatsApp may mark your flow to Throttled if the endpoint becomes unstable. For example, due to slow response times or repeated errors. While throttled, sending is limited to 10 messages per hour.

If the flow's endpoint health improves, it will transition back to Published.

If conditions worsen, WhatsApp can block it.
BlockedBlocked flows occur when endpoint performance significantly deteriorates. This is done to ensure that users are not exposed to degraded experiences. While in this state, the flow cannot be sent or opened.

If the endpoint improves, WhatsApp can revert the flow status to Throttled and eventually to Published.
Note

Only draft Flows can be fully deleted. You can delete a draft flow using the Flow Builder interface inside the WhatsApp Manager (opens in a new tab) or our API.

WhatsApp - Flows lifecycle

Manage a Flow

You can manage WhatsApp Flows and monitor their status through the web interface (opens in a new tab) or use the WhatsApp API flow actions for full programmatic control.

In the web interface, you can view WhatsApp Flows at both channel and sender levels.


View Flows at the channel level

  1. In the web interface (opens in a new tab), navigate to Channels and Numbers > Channels and select WhatsApp.

  2. Open the Flows tab to see all your flows.

    • You will find details such as the WABA they belong to, Flow ID, First flow screen, and Status.
    • You can copy the Flow ID and First flow screen element for reference.
    WhatsApp - Flows channel level

View Flows at the sender level

  1. In the web interface (opens in a new tab), navigate to Channels and Numbers > Channels and select WhatsApp.

  2. Open the Senders tab.

  3. Select the three-dot menu next to the desired sender and choose View Flows.

    • You will see all Flows associated with the sender, including the Flow ID, First flow screen, and Status.
    • You can copy the Flow ID and First flow screen element if needed.
    • You can also change the status of your flows.
    WhatsApp - Flows sender level

Manage Flow status

In the web interface (opens in a new tab), you can change the status of a flow depending on its current status.

Note

Changing the flow status is available only at the sender level.

To change a flow's status, open the sender-level flows view. Then, select the three-dot menu next to the desired flow. Choose one of the available statuses to transition the flow.

  • Draft: You can publish or delete the flow.
  • Published: You can deprecate the Flow.
  • Throttled or Blocked: You can deprecate the flow to prevent further issues.
WhatsApp - Flows status change





Need assistance

Explore Infobip Tutorials

Encountering issues

Contact our support

What's new? Check out

Release Notes

Unsure about a term? See

Glossary
Service status

Copyright @ 2006-2025 Infobip ltd.

Service Terms & ConditionsPrivacy policyTerms of use