Why the check exists
A source file can move, be deleted, or gain different sharing after you prepared the batch. The plan you reviewed may no longer describe the current source. The safety check helps stop an outdated plan from being applied without another decision.
It starts automatically after approval. Read failures also matter: an unavailable source is not proof that nothing changed.
Choose the appropriate response
| Action | When to use it |
|---|---|
| Continue restoring access | Available only when the detected changes do not have a blocking severity. Review the differences and record the required change-control note. |
| Update the batch | Use when the current source must be rescanned or the plan rebuilt. Review and approve the updated result. |
| Cancel batch | Use when the prepared work should not proceed. Check any existing execution history separately. |
Do not force past blocking changes
Deleted or moved items, newly shared items, and permission drift can make the approved batch out of date. If the panel reports blocking changes, Continue restoring access is unavailable. Update the batch so the new paths, recipients, and access levels can be reviewed.
For a planned cutover, reduce unnecessary source changes during the reviewed execution window. Coordinate this with the tenant owners; the check itself does not place the source tenant into a user-facing freeze.
If a decision still appears pending
The background workflow must process the submitted decision. Allow the panel to refresh and follow the stage shown. If it fails, retain the batch/run ID and exact error for support instead of repeatedly submitting conflicting decisions.