Error Message Handling

  • 2 minute(s) read
Prev Next

Encountering errors is a possibility when sending Mogli Messages, but knowing how to interpret them effectively is an important part of reviewing and understanding your deliverability.

  1. Read the Error Message Carefully

    •  Take a moment to read the entire error message indicated by the Debug field on a Mogli Message record.

    •  Pay attention to any specific codes, numbers, or phrases that might indicate the problem.

  2. Determine how many messages have a Status of “Error”

    • Run a report to show the number of errors

    • Use the fields: SMS Number, Created date, Message, Status, Debug, and Message SID

    • Make the report public or share it within a folder


  3. Review Errored Messages

    • Messages with a Status of “Error” will frequently display an error code/description within the “Debug” field of the Mogli Message record

    • The “Debug” field can give you more information on why the message failed

    • Review the Common Error Codes Table (below)

  4. Open a case with our team

    • If you’re still having trouble determining the cause for a particular errored SMS record, or don’t see your error code listed in the table above, email help@mogli.com to start a new case with our Technical Support Team

    • Share all details on the messages that were attempted to send (ex. How it was sent, who it was sent by, how many were sent)

    • Share the report of the messages in “Error” Status

Common Error Codes

Error Code

Common debug

Additional details

40001, 30006

Not Routable

The destination is either a landline or a non-routable wireless number and doesn't have messaging capabilities.

40002, 30007

Blocked as spam - Temporary

The message body may contain keywords or verbiage that does not comply with 10DLC guidelines.

40008, 30008

Undeliverable

Various factors would cause this issue. Look to verify if messages have been sent successfully to this number in the past.

40010, 30034

Unregistered 10DLC Message

Message was sent from a number not associated with an approved A2P 10DLC Campaign

40012, 30005

Invalid messaging destination number

The “To” number may be invalid

40016

T-Mobile 10DLC Sending Limit Reached

Each brand is assigned a certain throughput limit based on its brand score. This error indicates that you've exceeded the daily message sending limit set by T-Mobile for your brand. The count gets reset every day at midnight PST.

40018

AT&T 10DLC Sending Limit Reached

This indicates that you've reached AT&T's sending limit for your brand on the 10DLC route. AT&T's sending limit is given in message parts per minute.

40300

Blocked due to STOP message

Previous opt out

63016

Failed to send freeform message because you are outside the allowed window. If you are using WhatsApp, please use a Message Template.

The message is not an approved WhatsApp template.

63024

Invalid WhatsApp message Recipient

Recipient’s number is not WhatsApp-enabled

30019


Content size exceeded carrier limit could be caused by to many characters, or bytes in the message. UCS-2 encoded messages could have different limitations than GSM encoded messages.

3003


Unreachable destination number

Additional Things to Note

  • Messages with an “Error” Status, a blank “Debug” field, and no "Message SID" likely did not make it out of your Salesforce Org. This can be caused by configuration issues, failed Flows or other custom automations

  • Message details are not retained by our messaging partners forever! The faster an incident is reported to the Technical Support team, the more effective our troubleshooting can be

  • For more information on best practices to improve your message deliverability, reach out to your Account Manager!