Loading

Marketing Cloud - Updates to Content Blocks referenced in an email are not included when sending via Journey Builder and Triggered Sends

Дата публикации: Nov 24, 2025
Описание
Emails, including referenced content blocks, are cached when a triggered send definition is created. Updating email content within Content Builder, including Content Blocks referenced by ContentBlockById, ContentBlockByName, and ContentBlockByKey AMPScript functions, will not automatically update the email used in a Journey Builder or triggered send definition. The send definition must be republished in order to reflect the changes.
Решение

When an event triggers an email in Marketing Cloud, it creates a copy of the email (including content blocks called from AMPScript functions such as ContentBlockByID, ContentBlockByKey, and ContentBlockByName). To refresh the email, the triggered send will need to be paused, published, and restarted. This can be completed in one of several ways:

1. Manually pause, republish, and restart the email in Email Studio
2. Create and publish a new version of your journey
3. Republish the email from within the journey 

Note: It may be possible to customize SSJS (Server-Side JavaScript) within a CloudPage to automatically republish the triggered send definitions. The following resources include documentation about retrieving and republishing triggered sends via SSJS: 
Retrieve Triggered Send
Publish Triggered Send

This is a temporary workaround due to the bug.

There is an open Known Issue where if you add an auto-suppression list, it will automatically republish email content (including these content block references).

This can be used as a method for mass republishing emails, but is only a temporary solution due to the functionality described in the above Known Issue.



 

Номер статьи базы знаний

000395768

 
Загрузка
Salesforce Help | Article