Skip to content

Dry runs and diffs

Dry-run performs scanning, mapping, target reads, and planning but does not execute the planned provider writes. It is the default safety mechanism for new profiles and changed rules.

Each diff entry shows:

  • source item and normalized source state;
  • target identifier and mapping reason;
  • current target state;
  • changed fields and planned state;
  • status such as preview, applied, reverted, skipped, unmatched, or conflict.

Use Apply for a single reviewed entry or Apply visible after filtering a run. Applied entries can be reverted only when the provider adapter supports a safe inverse operation and the stored before-state is still meaningful.

Revert is another live provider write. Review it with the same care as Apply, especially when the account changed outside Brokerr after the original run.

Dry-run detail with two planned AniList changes
A dry-run records the before state, planned fields, and mapping reason without writing them.