Skip to content

Runs and history

The Runs page shows batch cards with run number, group/profile context, mode, dry/live state, status, timestamp, and counts. Select a batch to view All or one profile child tab. Tabs filter metrics, errors, progress, and diff entries.

  • Preview: planned by a dry-run and not written.
  • Applied: provider write succeeded.
  • Reverted: an inverse write succeeded.
  • Unmatched: no target identifier was resolved.
  • Skipped: policy, ignore, media type, or protection prevented a write.
  • Conflict: two profiles planned different payloads for one target item.
  • Error: planning, read, or write failed.

Expand Target before/Planned after to understand why fields changed.

JSON preserves structured fields; CSV is easier to review in a spreadsheet. Neither export includes provider credentials.

Bulk actions operate on the currently visible eligible entries. Revert uses the stored before-state and is a live write; external provider changes after the run can make the old before-state undesirable.