Investigate an unattributed operation

In the web app's sidebar, select All Operations under Monitor and find the run with the Filter operations search bar and the Date column. An unattributed operation is present, with its command, status, and date intact, but its Database, Changelog, or Project cell shows a dash instead of a link.

If the operation is missing from the list entirely, reporting itself did not happen. Check that operation reporting is enabled in that environment and that the ingest URL is right. See Configure operation reporting.

Open the operation. The detail page shows exactly what arrived:

• The Database Details section carries an orange Unregistered badge when the database did not resolve to a registered connection, with a Register database action.

• The Changelog Details fields read Not recorded when no changelog was linked.

• In the context line under the header, an unregistered database shows its name as plain text without a link, and a missing changelog or project shows a dash.

This tells you which link failed: the database connection, the changelog, or both.

In the environment that ran the operation, read the identifiers Liquibase was configured with: LIQUIBASE_PLATFORM_CONNECTION_IDENTIFIER and LIQUIBASE_PLATFORM_CHANGELOG_IDENTIFIER, or their properties-file equivalents. Compare them character for character against the identifiers on your registered records.

The matching rules explain what you see. If an identifier is not set, the operation is attributed to your workspace's default connection or changelog. If an identifier is set but matches nothing in your workspace, the operation ships without that attribution instead of falling back to the default. That is why a typo produces an unattributed operation rather than an error.

The usual suspects are a typo, an identifier copied from another environment along with the pipeline configuration, or a record that was never registered at all.

Wrong identifier: Correct it where that environment's Liquibase runs.

Be sure to:

• Replace your_connection_identifier and your_changelog_identifier with the identifiers on your registered records

Missing record: Register it. Use the Register database action on the operation's Database Details section, or follow Register a database connection and Register a changelog.

Run any reporting command from that environment and confirm the new operation arrives with its Database and Changelog cells linked. Operations captured before the fix keep their missing links, which is why identifier hygiene is worth a moment at setup time. See Set up monitoring end to end.