C2M

Errors (ErrorSource_ErrorCode) Message Description
c2m_1001 Consumer ineligible to receive message The recipient number is not eligibile to receive messages for the specific channel. Please check if its a landline number or invalid number.
c2m_1015 Unsupported Media Type The media file type sent with the message is not supported. Please check the media format and try again.
c2m_1029 Too many requests - rate limit hit The request exceeded the allowed rate limit. Please reduce the request rate and retry.
c2m_1300 No engagement found for skill Engagement not found for the skill. Please check if the skill is added in Conversational Cloud and is also activated from C2M self-service web tool.
c2m_1400 Open conversation already exists There is an open conversation for this customer. Make sure all the conversation from this customer on the specific channel are closed, and retry.
c2m_1910 SMS error — "To" number is opted out The recipient's phone number has opted out of receiving SMS messages.
c2m_1911 SMS error — "To" number not reachable The recipient's phone number could not be reached.
c2m_1912 SMS error — "From" number is not valid for messaging The sending phone number is not enabled for SMS messaging.
c2m_5000 Unexpected error occured An internal error occured in sending this message. If this continues to fail, please contact LP support.
c2m_5401 Internal Server Error An internal error occured in sending this message. If this continues to fail, please contact LP support.
c2m_5403 Message sent failed — timeout error There was an internal timeout sending the message. If this continues to fail, please contact LP support.
c2m_5807 Media URL is not in the permitted URLs list The media URL (photo, document, video, etc) needs to be included in the permitted URLs list. Use the settings tab in the Proactive Web tool to add the base URL to the permitted list.

Proactive

Errors (ErrorSource_ErrorCode) Message Description
proactive_500 Message could not be sent This error can occur because of any of the following reasons: open conversation exists, invalid input, network errors, internal connector error. If this continues to fail in spite of no open conversations, please contact LP support.
proactive_1001 Consumer ineligible to receive message The recipient number is not eligibile to receive messages for the specifc channel. Please check if its a landline number or invalid number.
proactive_1029 Too many requests - rate limit hit The request exceeded the allowed rate limit. Please reduce the request rate and retry.
proactive_1301 Recipient validation failed Recipient validation failed while publishing campaign. If this continues to fail, please contact LP support.
proactive_1302 Too many variables used The template expects less variables for creating the message to the recipient.
proactive_1303 Insufficient variables The template expects more variables for creating the message to the recipient.
proactive_1304 Template not found The template was not found
proactive_1400 Open conversation already exists There is an open conversation for this customer. Make sure all the conversation from this customer on the specific channel are closed, and retry.
proactive_1401 Bad request / Invalid Input There was an internal error. If this continues to fail, please contact LP support.
proactive_1800 Open conversation already exists for InApp There is an open conversation for this customer on the InApp channel. Make sure all the conversation from this customer on the specific channel are closed, and retry.
proactive_5000 Unexpected error occured An internal error occured in sending this message. If this continues to fail, please contact LP support.
proactive_5002 Network error occured Network error occured. If this continues to fail, please contact LP support.
proactive_5401 Unknown error occured There was an internal error. If this continues to fail, please contact LP support.
proactive_5403 Internal error occured There was an error in internal connector component. If this continues to fail, please contact LP support.
proactive_5404 Account error There was an error with the account configuration. If this continues to fail, please contact LP support.
proactive_5803 InApp message sent failed Proactive message failed to be delivered to the in-app. If this continues to fail, please contact LP support.
proactive_5804 Unknown error occured There was an internal error. If this continues to fail, please contact LP support.

InApp

Errors (ErrorSource_ErrorCode) Message Description
proactive_16 InApp token not found There was an internal error. If this continues to fail, please contact LP support.
proactive_17 InApp failed to sent message There was an internal error. If this continues to fail, please contact LP support.
proactive_19 InApp certificate missing There was an internal error. If this continues to fail, please contact LP support.
proactive_26 InApp — Push notification disabled The recipient mobile device does not support InApp messaging
proactive_27 InApp — Mobile app does not support in app messaging The recipient mobile device does not support InApp messaging
proactive_28 InApp — Consumer is not authenticated There was an internal error. If this continues to fail, please contact LP support.

WhatsApp

Errors (ErrorSource_ErrorCode) Message Description
outbound_wa_4xx (outbound_wa_400) WhatsApp error — Generic bad request error Meta returns a 400 error code for various reasons.
outbound_wa_5xx (outbound_wa_500) WhatsApp error — Generic server error Message failed to send because of an unknown error. Try again later.
outbound_wa_<wa_error_code> (e.g. outbound_wa_131000) WhatsApp errors Check the WhatsApp API error code translation in Meta's error codes documentation.
outbound_wa_NTW_ERR Network error occured in connector Network error occured in internal connector component while processing WhatsApp message. If this continues to fail, please contact LP support.

Google RCS

Errors (ErrorSource_ErrorCode) Message Description
outbound_googlercs_<googlercs_error_code> (e.g. outbound_googlercs_40008) Google RCS errors (Telnyx gateway) Google RCS messages are routed through the Telnyx RCS Messaging Gateway. Check the Telnyx API error code translation in Telnyx's API errors documentation.
grcs_5810 Google RCS content validation failed The contentMessage object is missing or does not match any supported GRCS content type (text, media, standalone rich card, or carousel card). Connect To Messaging invite path only — HTTP 400.
grcs_5811 Google RCS rich card content validation failed The rich card's cardContent (standalone) or cardContents (carousel) structure is invalid - for example, a carousel with fewer than 2 or more than 10 cards, or an invalid cardWidth. Connect To Messaging invite path only — HTTP 400.
grcs_5812 Google RCS media content validation failed The media fileUrl is missing, empty, or does not match the required URL pattern. Connect To Messaging invite path only — HTTP 400.
grcs_5813 Google RCS rich card is missing required components The rich card (or a carousel card) is missing all of title, description, and media — at least one is required. Connect To Messaging invite path only — HTTP 400.

SMS (Twilio)

Errors (ErrorSource_ErrorCode) Message Description
outbound_twilio_NTW_ERR Network error occured in connector Network error occured in internal connector component while processing SMS message. If this continues to fail, please contact LP support.
outbound_twilio_<twilio_error_code> (e.g. outbound_twilio_20500) Twilio error — send time Raised by the messaging connector when Twilio rejects or fails to process the send request. Check the Twilio API error code translation in Twilio's API errors documentation.
twilio_<twilio_error_code> (e.g. twilio_30001) Twilio error — delivery status Raised by delivery-status processing when Twilio reports the message failed or was never confirmed delivered after sending. Check the Twilio API error code translation in Twilio's API errors documentation.
twilio_5008 No delivery response from Twilio or message is undelivered Message was sent successfully to the network service provider of the recipient, but there was no response from the provider that the message was delivered to the recipient. As there is no delivery response for 72 hours after the message was successfully sent, this sms message was marked as failed.

SMS (Telnyx)

Errors (ErrorSource_ErrorCode) Message Description
outbound_telnyx_<telnyx_error_code> (e.g. outbound_telnyx_20500) Telnyx error — send time Raised by the messaging connector when Telnyx rejects or fails to process the send request. Check the Telnyx API error code translation in Telnyx's API errors documentation.
telnyx_<telnyx_error_code> (e.g. telnyx_30001) Telnyx error — delivery status Raised by delivery-status processing when Telnyx reports the message failed or was never confirmed delivered after sending. Check the Telnyx API error code translation in Telnyx's API errors documentation.
telnyx_5008 No delivery response from Telnyx or message is undelivered Message was sent successfully to the network service provider of the recipient, but there was no response from the provider that the message was delivered to the recipient. As there is no delivery response for 72 hours after the message was successfully sent, this sms message was marked as failed.