63018: Rate limit exceeded for Channel
MESSAGING
ERROR
This error occurs when you send messages faster than the channel, sender, or account can process them.
- Your account is sending messages faster than its available throughput. When you exceed your account-based messages-per-second (MPS) rate, Twilio begins queuing messages.
- Your RCS sender exceeded the rate supported for that sender. RCS senders support 100 messages per second by default.
- Your WhatsApp sender exceeded the sender throughput configured for outbound traffic. By default, each WhatsApp sender supports 80 messages per second for text or media.
- Your WhatsApp business portfolio reached its messaging limit for business-initiated conversations that are outside the customer-service window. That limit is shared across senders in the same business portfolio.
- Your account is sending too many messages from a single phone number to the same WhatsApp recipient.
- Throttle your application so that it does not submit messages faster than the throughput available to your account or sender.
- For RCS traffic, spread requests over a longer period so that the sender stays within its default 100 MPS limit and messages do not need to be queued.
- For WhatsApp traffic, wait until capacity becomes available again before starting more business-initiated conversations. If your business portfolio messaging limit was reached, new conversations can start again as active conversations end.
- If you need higher sustained volume, distribute traffic across multiple approved senders by using a Sender Pool or a Messaging Service sender pool where your use case supports it.
- For WhatsApp text-only traffic, request higher sender throughput if your use case requires it. Media throughput cannot be increased beyond 80 MPS.
- For WhatsApp, reduce how frequently you send to the same recipient to avoid triggering this error.