- Task
- Version · 6.0
- Deliver
Exit a Flow file
Last updated: August 11, 2026
Using the Control command, exit, in a flow file allows you to exit running the flow if there are not any pending changesets present. This enhances your efficiency when using a flow file by eliminating the need to run checks on unchanged changesets or generate drift reports when no changes are being applied.
Procedure
Run the status command within the Flow file and set the next -type argument to -type: control.
Include the status command and type: control in the flow file
Note: If you want to use Labels, add them here. You must add them under the status command, not the exit command.
The exit command has two command arguments:
exitCode: 0This is an integer and does not require quotes in its syntax.exitMessage: "a string"
This is a string and requires quotes in its syntax.
Set the exitCode to 0-4 depending on the severity you want to trigger.
Set the exitMessage.
Example: Exiting with an error status of 0 because the database is up-to-date.
Set the if: "status.changeset.Count == 0".
This will trigger the command to exit if Liquibase detects there are no pending deployed changesets.
This completes all of the Flow file changes to enable the exit control command. Next, you will move back to the CLI to run the Flow.
Note: A child Flow cannot cause a parent flow to exit. status commands must be run in the same Flow file that contains the control being checked.
After you set up your Flow file, run the flow command in the CLI.
The type:control action runs, and if no new changesets are detected, Liquibase exits the Flow.