Introduction
Stop the automation pipeline for a device immediately and cleanly. Unlike a failed action, Exit Automation is an intentional early termination β use it when conditions make the rest of the pipeline unnecessary or inappropriate to run.
Exit Automation Action
From the automation pipeline in edit mode, click + and select Exit automation from the Flow category.
This action has no configuration fields. Its behavior is controlled entirely by where you place it in the pipeline and what conditions you attach.
Example: Add an Exit Automation action after a script that checks whether an application is already installed. Set a condition on the action: if a install_status variable equals already_installed, exit. Subsequent install actions only run when the application is actually missing.
π‘ TIP: Exit Automation is cleaner than chaining long Action Condition blocks on every subsequent step. One exit point at the right place keeps the pipeline readable and easier to troubleshoot.
Conditions
The Conditions section lets you restrict when this action runs β in this case, when the pipeline exits.
See Action Conditions for the full reference on condition types, operators, and values.
Additional Options
Expand Additional options for action name, failure behavior, output variable assignment, retries, and the enabled toggle.
See Actions Overview for the full reference on additional options available on every action.
FAQ
Does Exit Automation mark the run as failed? No β it's a clean stop, not a failure. The run is marked as complete (or exited) for that device.
What if Exit Automation has no condition attached? The pipeline always stops at that point for every device. This is rarely the intended behavior β almost always pair it with a condition.
Does exiting affect other devices in the same run? No. Each device runs the pipeline independently. Exit Automation only stops execution for the device that hits it.
Who can add or modify Exit Automation actions? Technicians with permission to edit automations in the relevant group. See Workspace β Permissions for access control configuration.


