Troubleshooting overview section-overview
Use this section to find the cause of a problem and how to fix it. It brings together the troubleshooting FAQ, the guides for journeys, and one page for each family of error codes. Start from the type of resource you need, or from the error code that you received.
Troubleshooting FAQ faq
The troubleshooting FAQ answers frequent questions across Journey Optimizer, such as fragments, email content and tracking, and the count of engageable profiles.
Troubleshoot journeys journeys-guides
- Troubleshoot journey errors: find and fix the errors that block the test or the publication of a journey.
- Journey validation errors: understand a journey validation error code.
- Troubleshoot journey execution: find out why profiles do not enter or progress through a live journey.
- Troubleshoot inbound actions: debug an inbound action that does not display or continues after a profile exits.
- Troubleshoot custom actions: check that a custom action and its API call work.
Troubleshoot error codes error-codes
Each page groups the errors of one feature, with the exact error message, the cause, and how to fix it. Use the family of the error code to open the right page, or go directly to the section that matches where the error occurs.
Read an error code read-error-code
An error code has a prefix that identifies the service, an error number, and an HTTP status. For example, AJOJAS-2030-400 is a journey validation error (prefix AJOJAS), number 2030, status 400. A code with the status 200 is a warning: it does not block saving or publishing.
For the structure of error codes and the steps to take before you contact support, see the error codes reference.
Find your error by family find-error
Campaigns and audiences
Errors on Action, API-triggered and Orchestrated campaigns, on relational schemas and datasets, and on audience composition.
Content authoring and personalization
Errors on the content of messages, on expressions and helpers, and on proofs and simulated users.
Fragments, multilingual content and landing pages
Errors on fragments and AEM content, translation, and landing pages.
Deliverability setup
Errors on subdomain delegation, DNS records, seed lists and IP warmup plans.
Custom channels, inbound actions and reporting
Errors on custom channel credentials, inbound actions and reporting datasets.
Error pages and sections by family pages
Open a family to see its error pages, the prefixes of its error codes, and the sections of each page.
These errors appear when you check, test or publish a journey. Go to the section that matches the activity or setting named in the message.
- Journey validation errors: Journeys: validation before test or publication
Prefixes: AJOJAS
Sections: Journey structure | Action activities | Events and reactions | License package limits (Select) | Versions, test mode, and size
These errors appear when you set up, schedule or activate an Action, API-triggered or Orchestrated campaign, when you define a relational schema or a dataset, and when you build and publish an audience composition.
- Campaign errors: Action and API-triggered campaigns, including schedules
Prefixes: CJMCMP, CJMRT 15xxxx
Sections: Audience | Schedule and approval | Rapid delivery - Orchestrated campaign errors: Orchestrated campaigns
Prefixes: CJMOC
Sections: Campaign status and lifecycle | Activities | Signals and chained campaigns - Relational schema and dataset errors: Relational schemas and datasets
Prefixes: CJMDMS
Sections: Files and formats | Primary key and version descriptor | Relationships - Audience composition errors: Audience composition
Prefixes: CJMRT 17xxxx
Sections: Enrichment | Publication, limits, and permissions
These errors appear when you validate or save the content of a message, when an expression or a helper cannot be resolved, and when you preview a message or use simulated users.
- Content authoring errors: Content of emails, push notifications, SMS, in-app messages, and direct mail, including message lifecycle and permissions
Prefixes: CJMMAS 10xx and 2xxx, CJMRT 030xxx, JOMAL
Sections: Email content | Push notifications | Message lifecycle and saving | Permissions - Personalization errors: Personalization expressions, helpers, and URL encryption keys
Prefixes: CJMTL, CJMRT 01xxxx, 07xxxx, 13xxxx, 0816xx
Sections: Variables and paths | Helpers | URL parameter encryption keys - Proof and simulation errors: Proofs, previews, and simulated users
Prefixes: CJMPTS, AJOTDS, CJMSAS
Sections: Proofs and previews | Simulated users
These errors appear when you publish a fragment or use AEM content, when you set up language settings and translations, and when you publish or edit a landing page.
- Fragments and AEM content errors: Fragments, AEM content fragments, and AEM assets
Prefixes: CJMMAS 11xx to 17xx and 81xx, AJOCBS, AJOAGS
Sections: Publishing fragments | AEM content fragments | AEM assets - Multilingual content errors: Multilingual content and translation
Prefixes: CJMMAS 51xx, CJMRT 0809xx, AJOCTO
Sections: Language settings | Translation projects - Landing page errors: Landing pages
Prefixes: CJMMAS 3xxx, 107x, and 130x
Sections: Publication and status | Forms and subscription lists | Expiration
These errors appear when you delegate a subdomain, create DNS records or seed lists, and when you upload, activate or run an IP warmup plan.
- Subdomain delegation and DNS errors: Subdomain delegation, DNS records, and seed lists
Prefixes: CJMRT 0806xx and 0808xx
Sections: Subdomain delegation | DNS records | Seed lists - IP warmup plan errors: IP warmup plans
Prefixes: CJMRT 18xxxx
Sections: Plan file | Runs and activation | Run failures
These errors appear when you configure custom channel credentials, when an inbound action runs, and when you set up reporting datasets.
- Custom channel, inbound action, and reporting dataset errors: Inbound actions, reporting datasets, and custom channel credentials
Prefixes: CJMIAS, CJMRPS, CJMRT 0817xx
Sections: Custom channels | Inbound actions | Reporting datasets
If your problem is not listed not-listed
- Look for the error code in the error codes reference.
- Check the troubleshooting FAQ and the journey guides above.
- If the problem persists, contact Adobe Support with the complete error code and the request ID.