I am reaching out because I am experiencing a recurring issue with my WhatsApp automation. Several of my flows are being automatically set to "Stopped" status by the system shortly after being published (usually within minutes), even without manual intervention.
Context of my setup:
-
Channel: WhatsApp.
-
Integration: I am using External Requests to send data to Make.com (Integromat) for a CRM integration.
-
Webhook Configuration: My external server (Make.com) is configured to send an immediate Webhook Response (Status 200) with a valid JSON payload to ensure the connection closes correctly and stays within the timeout limits.
The Incident:
Recently, I experienced a peak in traffic that caused a "400 Bad Request: Queue is full" error on the Make.com side. I suspect that this repeated error might have triggered an automated "Circuit Breaker" or a safety flag on Manychat’s backend, which is now proactively stopping my flows to prevent further failed requests.
What I have already verified:
-
24-hour Window: I am aware of the WhatsApp 24h policy. However, the flows are stopping even when testing within the window or using approved Templates.
-
External Request Logs: I can see the "Bad Request" logs, but the flows are being stopped globally, not just for specific users.
-
Flow Logic: The flows were working perfectly before this traffic spike.
