Customer experience | Sales, Customer Insights,...

How to diagnose why a Contact received an email when they should have exited a journey

(0) Share

Report

Posted on by BJ-20051632-0

121

I have had several cases where the journey logic doesn't behave the way I expect it to and I am trying to figure out why. In this case I have a renewal reminder journey set up. The entry trigger is based on the "Renewal Billing" table when a new record is created containing "NAPB" in the name and with a "Benefit Status" not equal to "New":

I have two Exit criteria. One is based on the "Paid Through Date" being updated on the Renewal Billing record (I'm not sure if this is linked to the same Renewal Billing record that fired the entry trigger to the journey, but I have a condition that the record should contain "NAPB" in the name since we have two associations we manage renewals for.

The second exit criteria is based on Segment logic because sometimes people will renew with a 3-year membership, which creates a new Renewal Billing record that isn't tied to the entry trigger. This was meant to be my failsafe so that no matter what, if someone had a "Paid Through Date" more than 4 months in the future, they would exit the journey.

Now, I have a Contact who entered the journey on 3/4/2026 (renewal invoice was created) and 3/23/2026 (she upgraded to the 3-year membership and a new invoice was created.

She never exited the journey and received 2 email reminders from us to renew even though she is on the Exit Segment.

How do I go about identifying where my logic has holes? Any guidance is appreciated. As I mentioned, this isn't the first time I thought my logic was airtight and the segment or journey didn't behave as I thought.

Categories:

Dynamics 365 Customer Insights - Journeys

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Suggested answer

11manish 962 on at

Like (0)

Report
Copy link

Link copied!

Based on what you've described, I'd investigate the segment evaluation timing and the fact that the renewal occurred on a different Renewal Billing record than the one that triggered the journey.

The first exit condition likely never fired because the update happened on a different record, and the second exit condition may not have evaluated the segment membership quickly enough (or the segment logic isn't referencing the correct renewal record).

The Journey Insights timeline for that specific contact should be your first stop—it usually provides the clearest evidence of exactly where the logic diverged from expectations.

Was this reply helpful? Yes No
BJ-20051632-0 121 on at

Like (0)

Report
Copy link

Link copied!

I can see that the emails were delivered on 5/22 and 6/11, which is consistent with her 3/23 entrance into the journey.

She renewed the membership on 3/23, which should have kicked her out of the journey based on the segment logic.

I can't see when she was added to the segment, only that she is on there now. (Or is there a way to see when she was added?) But if she was added on 3/23 that should have been plenty of time for her to be excluded before the 5/22 email.

The segment is based on Renewal Billing - I can't select which RB record to look at, but I assumed if ANY of a Contact's RB records match the criteria, they would be excluded. Is this the correct assumption?

Was this reply helpful? Yes No
Suggested answer

ManoVerse 1,281 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Your event exit only listens to the original Renewal Billing record (3/4) -> the 3/23 renewal created a new record, so exit never fired , your segment exit worked logically, but in RTJ it is not processed in time to stop emails
RTJ does not re-check segment membership before sending emails
What you can do to fix this:
1) Fix the exit trigger , use it on any renewal billing record(created or updated) for that contact, this will remove the wrong record issue completely
Don’t rely on segment for exit control
Keep segment for Audience / reporting and not for stopping live journeys

Also you can put condition before ever mail send like
If Paid through date < Today + 4 months
then send email
else
dont send , get exit

Was this reply helpful? Yes No
BJ-20051632-0 121 on at

Like (0)

Report
Copy link

Link copied!

RTJ does not re-check segment membership before sending emails

This I did not know! I assumed that anytime someone was added to the segment, they would get kicked out.

1) Fix the exit trigger , use it on any renewal billing record(created or updated) for that contact, this will remove the wrong record issue completely

Do you know how I can set up the exit trigger so it is based on ANY renewal billing record, not just the one that triggered the journey entry? Because we run memberships for multiple societies, we do not have a "Paid Through Date" field on the Contact record - it exists only on the Renewal Billing Records.

Was this reply helpful? Yes No
Suggested answer

ManoVerse 1,281 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

What you want to do is create a trigger that listens for changes on the Renewal Billing table, instead of trying to tie it to a specific record.
Start by going into Customer Insights – Journeys -> Triggers and creating a new trigger. Choose the Renewal Billing table, and set it to fire when a record is created or updated. This ensures it runs every time any billing record changes, not just one.
Next, you need to make sure the trigger is linked back to the Contact. In the trigger setup, find the Contact lookup field on the Renewal Billing record and use that as the reference. This will tell the system that whenever any billing record changes, connect that event to this Contact. by this your trigger is no longer tied to a single record, it’s tied to the person, which is exactly what you need.
If needed, you can also add a condition as per your need( only trigger when the status becomes “Paid” or when the Paid Through Date is updated), so people don’t exit the journey on every minor update.
Finally, go into your journey, open the Exit criteria, and select “Exit when a trigger occurs”, then choose the trigger you just created.
This will create behavior like : Any Renewal Billing record for that contact gets created or updated -> the trigger fires -> the contact exits the journey immediately
So even if they have multiple memberships or multiple billing records across different societies, it still works cleanly because everything is driven off the Contact, not a single record.

Was this reply helpful? Yes No