Loading

Salesforce Digital Engagement: Enhanced Messaging Error Codes — Feature Parity Gap with Legacy LiveAgent

Julkaisupäivä: Jul 21, 2026
Kuvaus

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.

Ratkaisu

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.

Knowledge-artikkelin numero

005386537

 
Ladataan
Salesforce Help | Article