* Digital Engagement *

Hola, Monica!

Ese error normalmente aparece cuando el número o la estructura de los parámetros del componente de mensajería no coincide exactamente con los parámetros de la plantilla de WhatsApp aprobada por Meta.

Revisaría estos puntos:

• Compara el número de variables de la plantilla de Meta ({{1}}, {{2}}, etc.) con los parámetros configurados en el componente de Salesforce.
• Verifica que no haya variables adicionales o que falte alguna.
• Revisa especialmente los parámetros de Header, Body y Buttons, ya que deben corresponder con la plantilla aprobada.
• Si modificaste la plantilla después de crear el componente, prueba a volver a sincronizar/recrear el componente con la plantilla actual.
• Asegúrate de estar utilizando exactamente la misma plantilla aprobada y versión en Salesforce y Meta.

Por ejemplo, si la plantilla tiene Hola {{1}}, tu número de caso es {{2}}, el componente debe proporcionar exactamente esos dos parámetros.

Si compartes una captura de la configuración del componente y de la plantilla de Meta (ocultando datos sensibles), sería más fácil identificar cuál de los parámetros no coincide.

Hi Team,

I faced the same issue and found a solution that worked for me.

My requirement was to link a newly created Messaging Session to the Case from which the session was initiated using a Screen Flow.

Solution:

Enable Change Data Capture (CDC) for the Messaging Session object in Setup. This publishes a change event whenever an action occurs on a Messaging Session record, such as create, update, or delete. The event message provides the Messaging Session record ID and its field values, including the Messaging User ID.

First, store the Case ID on the Messaging User record within the Screen Flow (or from wherever you are initiating the Messaging Session).

Since a Messaging Session change event is published whenever an event occurs on the record, subscribe to it using either a Platform Event-Triggered Flow or an Apex Trigger on the Messaging Session Change Event. Then perform the required logic:

1. Retrieve the Messaging User ID from the Messaging Session event.
2. Use the Messaging User record to get the Case ID that was stored earlier.
3. Update the Messaging Session record using the Messaging Session ID received in the event and the Case ID which we get by query the messaging user.

This will successfully link the Messaging Session to the Case.

If you need code samples or additional guidance for implementing this solution, please reply to this comment. 

Thanks.

Hi @Sven Riemer

, 

I am also at same situation and I tried reverting Embedded Service Deployment to v1 but still no luck. Did you manage to get this working with v1, if so was there any additional change needed? 

Thank you.. 

Manoj