ÃÛ¶¹ÊÓƵ

Documentation

ÃÛ¶¹ÊÓƵ Journey Optimizer: Multilingual feature gets “Message validation error (CJMMAS - 1069-500)â€

Last update: Mon Apr 07 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

In ÃÛ¶¹ÊÓƵ Journey Optimizer, a Message Validation Error (CJMMAS - 1069-500)  linked to the multilingual feature prevents journeys from being set to test mode or published. This article provides steps for resolution.

Description description

Environment

  • ÃÛ¶¹ÊÓƵ Journey Optimizer (AJO)
  • Feature: Multilingual capability

Issue/Symptoms

The following error message appears when you attempt to activate or publish journeys using the multilingual feature:  “Message Validation Error (CJMMAS - 1069-500).â€
This error prevents journeys from being set to test mode or published.

Symptoms include:

  • Locale selection is restricted to a single language (for example, Italian).
  • Errors are caused by naming conventions of content templates or improper handling of HTML components.

Resolution resolution

To resolve this issue, follow these recommendations:

  1. Ensure all required fields (for example, subject line, body, from/reply addresses) are populated for each locale. Remove any empty placeholders.
  2. Verify that translations and fallback languages are properly populated before activation.
  3. Open email content in Email Designer and validate each language version separately. Correct any incomplete personalization tokens or mismatched field types (for example, language code or locale mismatch).
  4. Create content directly through UI rather than importing HTML. This ensures compatibility with the multilingual feature.
    • If using HTML components is necessary, generate code via the UI first and base your customizations on it. Although this approach doesn’t guarantee success, it may reduce errors.
  5. Use appropriate naming conventions for content templates and avoid names that could conflict with locale mapping. Label templates clearly without suffixes unrelated to locales.
  6. Review if automation scripts were used during template creation. Ensure they align with AJO’s requirements for multilingual functionality.
  7. Importing HTML directly into AJO can lead to structural issues within the UI if tags are improperly formatted. Avoid editing imported HTML in ways that disregard tag structure when using fragments or templates.

Get started with multilingual content in the Journey Optimizer Guide

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f