Your email can be aborted if the template contains the {% abort %} command. This command stops code execution for customers who meet specific Jinja conditions.
When {% abort %} is used in an email node, the email isn't sent, and the customer doesn't continue to the following nodes in the scenario flow.
How to check this
Review the template used in the email node and look for one of these Jinja tags:
{% abort %}{% abort: "Custom message" %}You can view the number of abort runs in the scenario's evaluate tab by hovering over the email node.
If you want to learn more about how to use this feature, refer to our documentation.
How to prevent aborts
Make sure customer profiles who should not receive the email are filtered out before they reach the email node. This keeps the email logic simpler and helps avoid unnecessary aborts.
Note
The abort tag is also available in other action nodes, such as SMS, Mobile push, and Webhook, and more.
It is also available in non-action nodes, such as condition, wait, and limit nodes. In those cases, no event is added, even if you provide a reason.