There are several reasons a Contact isn’t sent an email from Journey Builder. There are two parts to troubleshooting Emails sent via Journey Builder; the Journey and the Triggered Send used by the Journey to send the email. This article discusses the most common reasons a Contact won’t receive an email in a Single Send and Multi-Step Journey.
For details on troubleshooting a Triggered Send review Marketing Cloud Engagement Triggered Send Not Sent to Subscriber.
Table of Contents:
The first thing to check is if the Contact made it to the Journey’s Email Activity. To complete these steps, you must know the Journey that contains the Email Activity and the Contact Key of the Contact who didn’t receive the email.
If the Contact made it to the Email Activity and was successfully processed, it doesn’t guarantee the email was sent to your Contact. It means Journey Builder successfully passed the Contact Key (and data) to the Triggered Send to deliver the message.
Follow the Knowledge Article Marketing Cloud Engagement Triggered Send Not Sent to Subscriber to troubleshoot the triggered send used by Journey Builder.
If the Contact didn’t make it to the Email Activity, our next step is to confirm the Contact met the Entry Criteria and was successfully injected into the Journey.
After confirming the Contact didn’t make it to the Email Activity step, check the Contact was successfully injected into the Journey.
Every Journey requires an Entry Source to determine if a Contact is eligible for the Journey. If the Contact meets the requirements of the Event Entry Source, it is injected by the Journey. If the Contact doesn’t meet the criteria, it won’t be injected and processed by the Journey.
To verify the Contact has been injected and is eligible for the email, you need their Contact Key. Once you have their Contact Key, use the following steps to check the Entry Results.
Alternatively, you can check Journey injection via the History tab within Journey Builder.
You’ll be looking for the ActivityType of TRIGGER and a Status of MetCriteria. 'Trigger' is the original name for the Entry Source of the Journey. Review Status Key Reference for more information on each status.
If the Journey didn’t accept the Contact, review the Contacts data and the Event Entry Source filter criteria to identify why the Contact didn’t meet the requirements.
If you’re using a Multi-Step Journey and the Contact was injected but didn’t make it to the Email Activity, proceed to the next section to review the Contact's path in the Journey.
If your Journey is a Multi-Step Journey and the Contact was injected but didn’t make it to the Email Activity, the Contact likely followed a path in the Journey that didn’t lead to the Email Activity.
Use the View a Contact Path to confirm the path your Contact took once injected into the Journey and review the Activities and path the Contact took.
Specifically, look for your Contact to move through the Email Activity you expect to be sent. Ensure the highlighted path navigates through the Email Activity, and you see a Continue (green dot) status for the Email Activity in the Contact Path details section.
When a Journey Builder Email Activity successfully processes a Contact, the Contact is sent to the Triggered Send associated with that email. Follow the steps outlined in Marketing Cloud Engagement Triggered Send Not Sent to Subscriber to troubleshoot the triggered send used by Journey Builder.
Journey Builder email delivery depends on two systems working correctly: the Journey itself and the underlying Triggered Send. A Contact may be excluded at any of the following stages — each with a different resolution path:,
000393333

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.