In Legacy (LiveAgent) Chat and SMS it was possible to capture error details via the ConversationEntry object's MessageStatus and MessageStatusCode fields.
With Enhanced messaging channels, this object and its fields are no longer available to easily identify and act upon failed messages programmatically via the REST API for example.
This is a known feature parity gap between standard and enhanced messaging and instead Messaging Error Codes are presented within the messaging session.
If you would like to see similar functionality added to enhanced messaging with a future release, please consider creating or promoting an Idea on the IdeaExchange.
Alternatively, ask Support to reference the internal information section of this article to add your Account to the internal record to track customer impact for the Product Team's consideration.
005386537

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.