Messaging component out of sync status in Salesforce

Overview:

In certain scenarios, the Messaging Component in Salesforce may display an “out of sync” error related to changes in Meta (WhatsApp). This issue can prevent the component from functioning as expected, causing agents to be unable to use it within Enhanced Conversations.

Error Message:

When attempting to open the Messaging Component, the following error is displayed:

“The messaging component is out of sync with changes made in Meta. To override the changes in Meta, reactivate the component in Salesforce.”

Standard Behavior / Common Cause:

This issue typically occurs due to how template synchronization works between Salesforce and Meta (WhatsApp Business Account - WABA):

>When templates are created or edited in Salesforce using the Messaging Component Builder, the changes are synced with Meta.
>If the same template is later modified directly in Meta (WABA), Salesforce detects a mismatch.
>As a result, the Notification Messaging Component in Salesforce is marked as out of sync.

Resolution in Standard Scenarios:

To resolve this:

>Recreate the changes within Salesforce.
>Activate the template again in Salesforce.
>This republishes the latest version to Meta and restores synchronization.

Alternatively:

Reactivating the Messaging Component in Salesforce overrides the changes made in Meta.

Rare Scenario ("No Changes in Salesforce or Meta"):

================================

In very rare cases, customers may encounter the “out of sync” status even when no changes were made in either Salesforce or Meta.

This behavior is due to an internal synchronization timing issue rather than an actual data mismatch.

Technical Explanation:

When a Messaging Component (Flow template) is saved and activated:

>Salesforce publishes the flow to Meta (WhatsApp).
>Meta processes the request and sends back confirmation events to Salesforce indicating the updated flow status.
>Salesforce relies on these confirmation events to maintain synchronization status.

To ensure data integrity:

>Salesforce validates whether the confirmation event is received within an expected time window after the most recent save operation.
>This mechanism prevents unintended overwrites from external (non-Salesforce) changes.

In this specific rare scenario:

>Meta sends the confirmation event while the activation request is still being processed on the Salesforce side.
>At that moment, Salesforce has not yet recorded the latest save timestamp.
>When the confirmation event arrives:
   a. It is compared against an older timestamp.
   b. It appears to fall outside the expected time window.
>As a result, Salesforce incorrectly interprets this as an external change and marks the component as out of sync.

This is a classic race condition, where two asynchronous processes (Salesforce activation and Meta confirmation) occur out of the expected sequence.

Important Clarification:

>There is no actual data mismatch between Salesforce and Meta.
>The flow configuration on Meta is correct and fully aligned with Salesforce.
>The issue is purely due to timing of event processing, not user actions or configuration errors.