Loading

Marketing Cloud Engagement | Email Content Discrepancy Between Journey Builder Canvas Preview and Actual Sent Emails

Udgivelsesdato: May 13, 2026
Beskrivelse
This article addresses a scenario where email updates made in Content Builder are not reflected in emails received through Journey Builder.
Understanding how Journey Builder send jobs lock content helps you apply the correct resolution — either by versioning the journey or re-selecting the activity — so that the latest message content is reflected in outgoing sends.

Common examples of related inquiries:
  • Email body changes made in Journey Builder are not reflected
  • The email body sent through Journey Builder differs from what is displayed on the Journey Builder canvas
  • The subject line/Preheader was updated and the version was incremented (or the job was updated) in Content Builder, but the subject line/Preheader change is not applied
Løsning

Reason why content discrepancies occur between Content Builder and Journey Builder

Journey Builder email activities are processed internally as trigger-based send jobs. The email content referenced by a send job is locked at the time the journey is activated, or when an activity is updated (by clicking Done). Because of this, editing and saving an email in Content Builder alone does not update the content of emails sent by a running journey.

 

Resolution

Use one of the following methods to reflect the latest email content in the send job.

If possible, add a test contact to the journey after making updates to confirm that the updated email is sent on the first entry. Note that this may not be feasible depending on the journey entry source, such as API-triggered entries.

 

 

A. Create a new version of the journey (Recommended)

Create a new version of the running journey and activate it. When the new version is activated, a new trigger send job is automatically created using the latest content — this is the most reliable method to reflect updates. Use methods B or C below only when creating a new version is not feasible.

 

B. Update the activity directly in Journey Builder

  1. Open the canvas of the running journey and click the target email activity.
  2. From the pull-down menu in the upper-left of the screen, select Activity Summary.
  3. If necessary, re-save from Edit Message, then click Done at the bottom of the screen.


Important: Do not navigate away or close the tab while the "Saving... do not exit this window" loading screen is displayed. Closing the screen mid-process may interrupt the job update, leaving email sends in a queued/suspended state.

Reference:  Marketing Cloud Engagement | Troubleshooting Emails Not Sent from Journey Builder

If you are using AMPscript or ContentBlockByID to reference content blocks and want to ensure those updates are reflected, method C may also be required.

Reference: Marketing Cloud - Updates to Content Blocks referenced in an email are not included when sending via Journey Builder and Triggered Sends
 
C. Update from Triggered Sends in Email Studio

  1. Go to Email Studio > Interactions > Triggered Emails.
  2. Expand the Journey Builder Sends folder, then open the folder for the relevant journey and version.
  3. Select the relevant triggered send and click Pause.
  4. Select the triggered send again and click Publish Changes.
  5. Select the triggered send one more time and click Start/Restart to restart sends.
 

Important: Always check "Message Configuration" when updating the subject line or Preheader

The subject line and Preheader of sent emails are stored in the Message Configuration option within the Journey Builder email activity — not in the Content Builder email asset. Updating the subject line or Preheader in Content Builder does not automatically reflect in Journey Builder.

To update the subject line or Preheader in a running journey, directly edit the text in Message Configuration within the email activity using the method B flow, then click Done.

Important:
Even when creating a new journey version (method A), the subject line and Preheader settings from the existing email activity are carried over as-is. Always open the email activity, verify and update the subject line and Preheader in Message Configuration, then save the activity before publishing the new version.

 
 

FAQ

Q. After updating content in Content Builder, the preview in the Journey Builder email activity appears to reflect the update — but the actual sent email content is different. Why?

A. The preview shown here fetches and displays the latest content at that point in time. It does not display the content that will actually be sent (which was locked at activation or at the previous update).

 

Summary: Email Update Procedures for Active Journeys

Depending on what you need to update (email body, or subject line/Preheader), follow the appropriate procedure below.

1. To update the email body:
Use one of the following methods:

  • Journey version upgrade (Recommended / Method A): Create a new version of the journey and update the email content.
  • Update the email activity (Method B): Directly update the target email activity within the running journey.
  • Update from Email Studio (Method C): If the email uses AMPscript referencing external content such as ContentBlockById, update and publish from Triggered Emails in Email Studio.


2. To update the subject line or preheader (Note):
Do not rely solely on the subject line/Preheader values in the Content Builder asset or email preview. Verify that the subject line and Preheader values in the Message Configuration option of the Journey Builder email activity match the intended values before completing the activity update.

Important note for version upgrades:
Even when creating a new journey version (Method A), subject line and Preheader changes in Message Configuration are NOT automatically reflected from the latest Content Builder values. Always confirm and update the subject line and Preheader in Message Configuration before publishing the new version.
Vidensartikelnummer

005321992

 
Indlæser
Salesforce Help | Article