​

Flow Health and Monitoring

It is important to monitor your Flow’s health and address any problems as they are discovered by WhatsApp. In order to do this, subscribe to and monitor the flow webhooks. You will receive multiple alert webhooks before the Flow becomes Throttled or Blocked. See Quality system overview below for more information. Flow health and monitoring is only applicable to Flows that use data from your endpoint.

​

Quality system overview

WhatsApp monitors and sends alert webhooks related to the following metrics:

• Endpoint or Client error rate
• Endpoint latency
• Endpoint availability

If any of these metrics deteriorate significantly, WhatsApp may throttle or block your Flow. When a Flow’s endpoint metrics begin deteriorating, the Flow status will first move to Throttled. Only if metrics deteriorate further is it moved to Blocked. Once a Flow’s endpoint recovers, it will move first from Blocked to Throttled, and then from Throttled back to Published.

​

How to get your Flow back to a Published state

1. Review the webhook alerts you have received for the Flow and check the contents of the alert.
2. If you you have received:
   • Latency alert
     • Improve the responsiveness of your endpoint (aim to return a response in less than 1 second).
   • Availability alert
     • Ensure that your endpoint is available continuously, and is reachable from the internet.
     • Check that your endpoint can correctly respond to health check ping requests.
   • Error rate alert
     • Review the errors listed in the alert and check the error codes reference guide for possible resolutions.

Once you have fixed your endpoint, WhatsApp monitoring automatically detects the changes and the Flow’s state is updated.

​

Publishing checks

←\ \ Previous\ \ Implementing Endpoint for Flows →\ \ Next\ \ Best Practices On This Page Flow Health and Monitoring Quality system overview How to get your Flow back to a Published state Publishing checks