14107: SMS send rate limit exceeded

This error occurs when your application sends more than 30 outbound replies between the same two phone numbers within 30 seconds. This safeguard helps stop auto-reply loops and runaway messaging jobs. After the limit is exceeded, messages in that conversation are marked failed for 30 seconds.

• Your application sends repeated replies between the same two phone numbers in a short time window.
• A <Message> action URL points to a TwiML document that sends another reply to the same conversation.
• A <Redirect> URL loops back to the same TwiML document and keeps generating replies.
• A webhook handler, background job, or REST API client is caught in a loop and keeps sending messages to the same recipient.
• An end user triggers automated replies rapidly enough to exceed 30 outbound replies in 30 seconds.

• Review your messaging workflow and confirm each inbound webhook triggers only the reply you intend to send.
• Check every <Message> action URL and <Redirect> target. Make sure they don't return TwiML that sends another reply to the same conversation unless that behavior is intentional.
• If you send messages with the REST API, add safeguards such as retry limits, loop detection, and duplicate request protection before sending another message to the same recipient.
• Test your webhook and TwiML flows end to end so you can confirm control doesn't return to the same reply path repeatedly.
• If you need this safeguard disabled for your account, contact Support only after you have protections in place to prevent costly auto-reply loops.

• TwiML for Programmable Messaging
• TwiML Message
• Understanding Twilio Rate Limits and Message Queues