Unable to send an Outbound Message in Messaging

Run a query using the fields from the ConversationEntry SOAP API Documentation. 

These are the error messages that you may encounter, along with with their MessageStatusCode: 

1. Error message is 'Can't send the message right now. Try again later' and MessageStatusCode is '9999'

- This throws '#551 - This person isn't available at the moment' on Facebook and this issue appears when a customer turned off messages on the Facebook Messenger to a page they are having conversation. Unfortunately, Facebook doesn't disclose specifics of these reasons to protect the user privacy.

Related Facebook Documentation:
Facebook Error Codes
How do I turn messages from a business on or off in Messenger?



2. Error message is 'Can't send this message because the message body is too large' and MessageStatusCode is '3004'

- This appears when the number of characters sent in a single message is higher than the maximum limit of 1994 characters for Facebook Messenger Channel and 908 characters for SMS Channel.
- Please note the standard text is 1 byte per character, but if an emoji is included in the message body, it converts the whole body to unicode which is 4 bytes per character. As a result, messages can have an appearance of being within the character limit and still fail to send. 



3. Error message is 'Can't contact the messaging service right now. Ask your admin to check the channel settings' and MessageStatusCode is '003'

- This message appears if the session has been invalidated because the user changed their password or Facebook has changed the session for security reasons. This is not a Salesforce messaging issue but rather a Facebook API error/warning message which triggered due to a Facebook invalid access token.
- To resolve this, re-authorize the Messaging Channel by clicking the 'New Channel' from the Messaging Settings page and re-add the channel.

Related Content:
Set Up Facebook Messenger Channels in Messaging



Note: The MessageStatusCode '9999' may result from different issues. We suggest to log a case to Salesforce Support Team and verify the issue encountered.