Dry Run Using Events | Community
Skip to main content
P
PaulTaylor
Level 2
February 3, 2026
Solved

Dry Run Using Events

  • February 3, 2026
  • 2 replies
  • 48 views

Does anyone have any experience using the Dry Run mode in AJO with either events as a condition within a journey or as an entry point?  I’ve been using it recently and whilst it works fine for batch qualified audiences, I’ve not seen any results when using events?

Thanks,

Paul

    Best answer by giriprasathb

    Hi ​@PaulTaylor ,Yes.this behavior is expected.

    Batch Audience Entry
    Dry Run works correctly for batch audience–based journeys because the qualified audience snapshot is already available. The system can simulate journey execution in a deterministic way using that existing audience data.

    Event-Based Entry or Event Conditions
    When using events (either as the entry source or as a condition within the journey), Dry Run has certain limitations:

    • It does not automatically simulate real-time streaming events.

    • A valid event payload must be triggered while the Dry Run session is active.

    • The event must resolve to an existing profile with properly configured identity mapping.

    If no qualifying event is received and processed during the session, the journey will not execute, which is why no results are visible in event-driven scenarios.

    Recommendation
    For validating event-triggered journeys, it is more reliable to publish the journey in a test sandbox and trigger a real event via Web SDK or API, then monitor execution through the profile timeline and journey reporting

    Thanks,
    Giriprasath B

    2 replies

    giriprasathb
    giriprasathbAccepted solution
    Level 3
    February 3, 2026

    Hi ​@PaulTaylor ,Yes.this behavior is expected.

    Batch Audience Entry
    Dry Run works correctly for batch audience–based journeys because the qualified audience snapshot is already available. The system can simulate journey execution in a deterministic way using that existing audience data.

    Event-Based Entry or Event Conditions
    When using events (either as the entry source or as a condition within the journey), Dry Run has certain limitations:

    • It does not automatically simulate real-time streaming events.

    • A valid event payload must be triggered while the Dry Run session is active.

    • The event must resolve to an existing profile with properly configured identity mapping.

    If no qualifying event is received and processed during the session, the journey will not execute, which is why no results are visible in event-driven scenarios.

    Recommendation
    For validating event-triggered journeys, it is more reliable to publish the journey in a test sandbox and trigger a real event via Web SDK or API, then monitor execution through the profile timeline and journey reporting

    Thanks,
    Giriprasath B

    P
    PaulTaylorAuthor
    Level 2
    February 11, 2026

    Thanks for the response Giriprasath, we identified in the end that we’d set the wrong namespace in the initial event and after fixing that can see that it’s working as expected.  Your response helped us to get the answer so again many thanks.

    Anuhya-Y
    Community Advisor
    Anuhya-YCommunity Advisor
    Community Advisor
    February 3, 2026

    ​@PaulTaylor Dry run works with unitary event journeys as well

    An easy way to validate this is:

    1. Create a unitary journey based on the business use case (for example, name it “abc – dry run”).

    2. Duplicate the same journey and name it “abc – test run.”

    3. Activate the duplicated journey in Test mode and set the original journey to Dry Run mode.

    4. Trigger the event in the Test mode journey.

    Since both journeys use the same event, this will help you validate that the Dry Run journey is working as expected.

      Terms & ConditionsAccessibility statement

      Loading footer...