- Concept
- Version · 6.0
- Manage
Which Liquibase commands report to Liquibase Server?
Last updated: September 29, 2026
Which Liquibase commands the server reports on, and which are skipped.
the server only captures data from Liquibase commands that materially change the database, enforce policy, or detect drift. All other commands are silently skipped with no log capture, no API calls, and no additional CLI output.
This keeps the platform focused on meaningful operations and avoids unnecessary API traffic.
Commands that are captured
Update family
Commands that apply pending changes to the database.
Command | Description |
|---|---|
| Execute all pending changesets |
| Execute a specific number of pending changesets |
| Execute changesets up to a specified tag |
| Execute the next changeset in changelog order |
Rollback family
Commands that revert previously applied changes.
Command | Description |
|---|---|
| Roll back to a specified tag |
| Roll back a specific number of changesets |
| Roll back changesets to a specified date |
| Roll back changesets to a specified tag |
| Roll back the most recent single changeset |
| Roll back the most recent update |
Changelog sync
Commands that update the DATABASECHANGELOG tracking table without executing SQL.
Command | Description |
|---|---|
| Mark all pending changesets as executed |
| Mark changesets as executed up to a specified tag |
| Mark the next changeset as executed |
Policy checks
Command | Description |
|---|---|
| Execute policy checks against changelogs |
Note: Only checks run is captured. Other checks subcommands (checks show, checks create, checks delete, etc.) are informational and are not reported.
Drift detection
Command | Description |
|---|---|
| Compare two databases and report differences |
| Generate a changelog from database differences |
Commands that are not captured
The following command categories are excluded by design:
Category | Examples | Reason |
|---|---|---|
SQL preview |
| Preview only. No database change occurs |
Informational |
| No value to the server platform |
Destructive utilities |
| Not a tracked deployment operation |
Developer utilities |
| Changes are immediately reverted |
Checks management |
| Configuration commands. No check execution occurs |
Help |
| No operation to capture |
What you see when a command is skipped
When the server detects a command that isn't captured, it prints a message to stderr:
[LB-PLATFORM] Command 'status' is not captured by Change Intelligence.This message confirms the server is installed and working, but has intentionally skipped the command. No data is sent to the API.
Note: If you need a command captured that isn't on the list, contact your Liquibase account team or file a feature request.