- Concept
- Version · 6.0
- Monitor
Understand changesets included in an operation
Last updated: September 29, 2026
The per-changeset record inside a deployment. What executed, what was skipped, and what failed.
A deployment operation lists every changeset it processed, in execution order. Each entry shows the changeset id, author, and changelog path, along with its outcome. This is the ground truth of what a deployment actually changed.
How changesets are grouped
The operation details page separates the changesets into four tabs.
Tab | What it shows |
|---|---|
Run | Changesets that were deployed in this operation. A changeset that was rolled back during the operation appears here with a rolled back annotation, because it did run. |
Filtered out | Changesets excluded by label or context filters. |
Failed | Changesets that errored. The row shows the failure reason where it is available. |
Not deployed | Changesets that were not deployed because an earlier failure ended the operation. |
Reading the changeset list
Use it to confirm that the changesets you expected are the ones that ran, and to trace any entry back to its changelog file. In a failed run, it shows exactly which changeset stopped the deployment and which ones never ran. The surrounding context, including the command, database, and logs, is on the operation details page.