Contextual attibutes after exporting a journey to another sandbox

Question

Hi all,

I want to export a journey triggered by a custom unitary event from PRE to PROD environment. This journey is started by a custom event sent from a 3rd party platform and it sends an email to the customer/profile specified by the custom event. Email uses contextual attributes as content personalizarion.

Issue: After exporting the journey (and its dependencies), we see that the context attributes need to be re-added to the template inside the journey in order to get the journey published. However, I get this error when trying to do this:

Workaround: The only solution I have found is to delete the email action from the journey and add it again (with re-work configuring everything again). This is not ideal because it involves manual work in PROD environment.

I'd appreciate any help on this topic.

@mayank_gandhi @satheeskannak

Mayank_Gandhi · Accepted Answer

@luiscardenas I think this is documented somewhere, When you export/import journeys and dependencies, the mapping or schema linkage for contextual attributes sometimes breaks, or the imported message/template isn’t correctly flagged to accept contextual data.

Your current workaround is the only broadly “stable” method: delete, re-add, and remap the contextual attributes in the email configuration. This is manual but ensures everything gets linked properly. You can try try editing the message so its status is “draft,” go to the journey, enable editing, re-select the message. This sometimes forces the UI to recognize the contextual attributes, particularly if you modify the event or context payload mapping just before re-adding the message.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded