Exit Rules are condition-based, Cadence-specific rules about when to remove a record from a Cadence. Once created, they apply to all steps in the Cadence for which they are configured.
You can find Exit Rules from the Cadence object under Related items.
Exit Rules serve a similar purpose to Decision Points, but they are general where as Decision Points are specific. The goal of Exit Rules is to make creating Cadences faster and easier, with fewer steps, less repetition, and less maintenance.
If there is a scenario that should remove a record from a Cadence only at a specific juncture, adding a Decision Point step is the way to go. However, if there is a scenario that should always result in a record being removed from the Cadence, regardless of which step cadence member is in, this is the ideal time to create an Exit Rule because it will save you the need to create multiple Decision Points.
For example, you could create an Exit Rule that applies in the case of email events: if an email is ever bounced, then remove the record from its Cadence due to bad data. Or in the case of phone calls: if the call outcome is Not Interested, the record is removed from all further steps as the person has clearly stated they do not wish to engage further.
Auto-Launched Flows can now be used in Exit Rules by populating the Flow Api Name on the Exit Rule Object. A video demonstrating how to leverage this functionality is linked here. A video explaining the Flow shown in the last video is linked here.
If Exit Rules sound right for you, contact your Customer Success Manager to talk about how best to set up Exit Rules for your organization.