In Legacy (LiveAgent) Chat and SMS, it was possible to capture error details programmatically via the ConversationEntry object's MessageStatus and MessageStatusCode fields. These fields allowed developers to identify and act on failed messages via the Salesforce REST API.
With Enhanced Messaging channels — such as WhatsApp, SMS via Salesforce Digital Engagement, and Apple Messages for Business — the ConversationEntry object and its MessageStatus / MessageStatusCode fields are no longer available. This means it is not currently possible to identify failed messages programmatically via the REST API in the same way as Legacy LiveAgent Chat and SMS.
This is a known feature parity gap between standard (Legacy LiveAgent) messaging and Enhanced Messaging in Salesforce Digital Engagement. A feature parity gap means that a capability available in the older product version has not yet been replicated in the newer architecture.
In Enhanced Messaging channels, error information is surfaced directly within the Messaging Session record in Salesforce, through the Messaging Error Codes framework. Agents and supervisors can view error codes within the messaging session rather than querying the ConversationEntry object.
If you would like to see programmatic error access added to Enhanced Messaging in a future release, consider creating or upvoting an existing Idea on the IdeaExchange. The IdeaExchange is Salesforce's public platform for customers to suggest and vote on product enhancements.
Alternatively, you can ask Salesforce Support to reference the internal information section of this article and add your account to the internal tracking record 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.