Simulate, version, and roll back a policy rule

Test a policy rule with a safe simulation, review its version history, and roll back to an earlier version when a change does not behave the way you expected.

Purpose

Confirm that a policy rule behaves the way you intend by simulating an action with no side effects, then use saved version history to compare changes and roll back if a recent edit is not what you wanted.

Who this is for

Owners and admins who want to test and manage policy changes safely before they affect real actions.

Prerequisites

You are signed in as a workspace owner or admin and Policy Studio is open.
At least one policy rule or template exists to test, or you are ready to create one.
A clear scenario in mind, such as publishing to connected accounts or exporting workspace data, so you know what you are checking.

Steps

Open Policy Studio and find the rule you want to test in the rule workspace.
In the Check a scenario panel, choose what you want to check, then select Check policy to run a safe simulation.
Read the simulation result to see whether the action is allowed, needs approval, or is blocked, along with the reason, affected resources, approver, and estimated cost.
If the result is not what you expected, edit the rule, save it, and run Check policy again to compare the new outcome.
Select History on the rule to open its version list and review each saved version, its change, and when it was saved.
Choose Roll back to this version on an earlier version to restore it, then run one more check to confirm the rule now behaves as intended.

Expected result

The simulation result shows a clear decision and reason without taking any live action, the rule history lists each saved version with the current one marked, and rolling back restores an earlier version that you can re-check to confirm.

Verification

The scenario panel confirms the check ran as a safe simulation, with nothing published and no provider action taken.
The simulation result shows a decision of allowed, approval needed, or blocked, with a plain-language reason and next action.
The rule history lists saved versions, marks the current one, and shows a confirmation after you roll back.

If something goes wrong

The simulation result still says it has not been checked.: Choose a scenario in the Check a scenario panel and select Check policy; the result fills in once the safe simulation finishes.
The simulation outcome is not what you expected for the rule.: The outcome follows the rule's Require approval and Block provider action settings and whether the rule is enabled, so adjust those, save, and run Check policy again to compare the fresh result before relying on it.
History shows only one version, so there is nothing to roll back to.: Roll back becomes available after a rule has been edited and saved more than once; make a change and save to start building its history.

Permissions

Only workspace owners and admins can simulate, edit, and roll back policy rules. Simulations are read-only previews; saving a change or rolling back updates the rule for everyone in your workspace and is recorded in the rule's history.

Support

If a simulation or rollback does not behave as expected, contact LumenReach support through the Help support path. Support can guide you using your rule names and version history without needing access to your credentials or any private workspace data.