Need Help Understanding AJO Journey Exclusion Error | Community
Skip to main content
C
chrisyan
Level 4
August 12, 2025
Solved

Need Help Understanding AJO Journey Exclusion Error

  • August 12, 2025
  • 1 reply
  • 479 views

Hi Team,

 

After running a journey in AJO and reviewing the "All Time Report," I noticed that some records were excluded under the Journey Exclusions section with the reason:
ERROR_SEGMENT_REALISATION_CONDITION_MISMATCH.

However, it's unclear what exactly caused these records to be excluded. Could you please advise on how and where I can get more detailed insights into this specific exclusion error to better understand and troubleshoot the issue?

 

Thank you.

Best answer by Mayank_Gandhi

@chrisyan difficult to say without seeing profile and checking without step events. The journey’s entry uses the most recent “profile snapshot” available at the time it executes, which may not reflect the very latest segment/audience definition, especially when journeys and segments are updated or triggered at overlapping times.

Best practice: Schedule your journey’s start after the batch segment evaluation and snapshot export complete each day, so the journey always has the latest audience picture.
https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-26253

1 reply

Mayank_Gandhi
Adobe Employee
Mayank_GandhiAdobe Employee
Adobe Employee
August 12, 2025

@chrisyan  This exclusion occurs when the journey is set up to accept only certain segment realization statuses (typically “realized”—meaning profiles entering or joining an audience), but the Journey receives profiles whose segment status does not match the expected condition (e.g., they are already "existing" in the segment, not newly realized). To dig deeper into who was excluded and why, you can use the Query Service((journey_step_events) with the relevant datasets:

SELECT DATE(timestamp),
       _experience.journeyOrchestration.profile.ID,
       _experience.journeyOrchestration.serviceEvents.dispatcher.projectionID
FROM journey_step_events
WHERE _experience.journeyOrchestration.serviceEvents.dispatcher.eventType = 'ERROR_SEGMENT_REALISATION_CONDITION_MISMATCH'

Example:
If a journey listens for segment entries (newly qualified profiles), but a profile was already in the audience before the journey started, that profile will not qualify at runtime and will be excluded for this error.

    C
    chrisyanAuthor
    Level 4
    August 12, 2025

    Thanks a lot! quick question that they're blocked at exit criteria looks like. my entry audience are batch evaluations run every 24 hours that should have removed bad profiles at audience level. why they're excluded even on the journey level with exit audience?

    Mayank_Gandhi
    Adobe Employee
    Mayank_GandhiAdobe EmployeeAccepted solution
    Adobe Employee
    August 12, 2025

    @chrisyan difficult to say without seeing profile and checking without step events. The journey’s entry uses the most recent “profile snapshot” available at the time it executes, which may not reflect the very latest segment/audience definition, especially when journeys and segments are updated or triggered at overlapping times.

    Best practice: Schedule your journey’s start after the batch segment evaluation and snapshot export complete each day, so the journey always has the latest audience picture.
    https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-26253

    Terms & ConditionsAccessibility statement

    Loading footer...