- Task
- Version · 6.0.2
- Improve
Investigate an unattributed operation
Last updated: November 17, 2026
An unattributed operation was captured but not linked to your registered records. Nothing failed, and the run completed, but the operation is invisible to every filter, project, and dashboard that organizes by database connection or changelog. The cause is a missing identifier: Liquibase named the connection but not the changelog, or the changelog but not the connection. An identifier that matches no registered record has a different result, because the server refuses the whole operation, so it never appears at all.
Before you begin
Contact us to enable Change Intelligence.
You have access to the environment that ran the operation, so you can read and correct its Liquibase configuration.
Procedure
Read what the server received
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.
Verify the fix
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.