Email creations during AJO upgrade | Community
Skip to main content
Selliers
Selliers
Level 4
January 29, 2026
Solved

Email creations during AJO upgrade

  • January 29, 2026
  • 1 reply
  • 35 views

We are experience lot of strange tings happening to out email when they are created during AJO updates. It seems to have some connection to our created email fragment that uses variables. Since it suddenly becomes problems with them, for a day or two. Then it goes back to normal. 

What happens is that fragments that uses variables, has a set av default values. In the templates where fragments is used and the default variables is changes to something else, they are reset to default in the templates they work on when the release is ongoing. 

This causes a lot of problems since out fragments has language and business areas values - when this changes it all becomes wrong. The logo changes to another business unit, and the footer becomes footer for another country and language. 

Can somebody confirm if our theory is correct, that a AJO release can effect emails that you are working on during the release.

Best answer by giriprasathb

Hi ​@Selliers ,Thank you for explaining the issue clearly. Based on AJO’s design, a platform release should not permanently reset or overwrite fragment variable overrides defined at the email template level.

In Journey Optimizer, fragment default values act only as fallbacks. When those variables are overridden within a template (For example, language, logo, or business unit footer), the overridden values are stored with that template and should persist independently of fragment defaults — even during system releases.

During deployment windows, temporary UI inconsistencies can occur due to caching or synchronization updates. In such cases, the editor may briefly display default values instead of overridden ones. However, once the release stabilizes, the correct saved values should reappear.

If the overrides are actually being replaced and remain changed after the release window, that would not be expected behavior and should be escalated to Adobe Support for investigation.


For reference:
AJO Fragments Documentation:
https://experienceleague.adobe.com/en/docs/journey-optimizer/using/content-management/fragments/fragments

Thanks,
Giriprasath B

1 reply

giriprasathb
giriprasathbAccepted solution
Level 3
February 5, 2026

Hi ​@Selliers ,Thank you for explaining the issue clearly. Based on AJO’s design, a platform release should not permanently reset or overwrite fragment variable overrides defined at the email template level.

In Journey Optimizer, fragment default values act only as fallbacks. When those variables are overridden within a template (For example, language, logo, or business unit footer), the overridden values are stored with that template and should persist independently of fragment defaults — even during system releases.

During deployment windows, temporary UI inconsistencies can occur due to caching or synchronization updates. In such cases, the editor may briefly display default values instead of overridden ones. However, once the release stabilizes, the correct saved values should reappear.

If the overrides are actually being replaced and remain changed after the release window, that would not be expected behavior and should be escalated to Adobe Support for investigation.


For reference:
AJO Fragments Documentation:
https://experienceleague.adobe.com/en/docs/journey-optimizer/using/content-management/fragments/fragments

Thanks,
Giriprasath B

    Terms & ConditionsAccessibility statement

    Loading footer...