Planning an Integration Dry Run
A dry run shows the changes a workflow intends to make before it writes them. It is valuable when a bulk operation is difficult to reverse or the matching rules are new.

Produce a reviewable change proposal
Display the matched record, current value, proposed value and reason for the change. Separate unchanged records from additions, updates and exceptions. Make it clear that the dry run has not applied the proposal, and ensure the later execution uses the reviewed scope.
Practical checklist
- Show before and after values.
- Include matching evidence.
- Separate exceptions from changes.
- Record the reviewed source version.
How to review the result
Approve a small proposal and compare it with the eventual result. A dry run is less useful if the data or rules change silently between review and execution.