Fix policy rule problems

When a policy rule is not behaving the way you expect, run a safe policy check and read the result's decision and reason. This guide walks through the most common Policy Studio problems: a rule that does not seem to take effect, an action that is blocked or asks for approval when you did not expect it, approvals that route to no one, and edits that left a rule in an unexpected state. Every check is a simulation, so nothing is published and no provider action is taken while you investigate.

Purpose

Diagnose why a policy rule is allowing, blocking, or requiring approval differently than you expected, and correct it safely using checks and rule history.

Who this is for

Owners and admins whose policy rule is allowing, blocking, or requiring approval differently than they expected.

Prerequisites

Access to Policy Studio for the workspace.
The action or scenario you want to check.
An owner or admin role for any change to a rule's status, conditions, approvers, or version.

Steps

Open Policy Studio, choose the scenario that matches the action you are testing, and select Check policy to run a safe simulation.
Read the simulation result: note whether it shows Allowed, Approval needed, or Blocked, and read the reason and next action it gives.
Remember the check is a combined result: it needs approval or blocks if any enabled rule has Require approval or Block provider action turned on, so a disabled rule is the most common reason an action is not governed as you expected.
Edit the rule that is forcing the outcome - its Require approval or Block provider action setting and its approvers - then save; saving records the rule but runs no provider action.
If an action needs approval but routes to no one, add at least one approver to the rule and save.
Run Check policy again and confirm the result now matches what you intended.

Expected result

The simulation result matches what you intended for that action, showing the decision and a plain-language reason, with no live action taken.

Verification

The simulation result shows the decision you expected (Allowed, Approval needed, or Blocked) with a matching reason.
A rule you enabled or edited shows the correct status and saved details when you reopen it.
After you add an approver, a result that needs approval names who must sign off.

If something goes wrong

A rule does not seem to take effect at all: Check its status; a rule marked Disabled is not counted in the check. Choose Enable, then run Check policy again.
An action needs approval or is blocked unexpectedly: The check needs approval or blocks if any enabled rule has Require approval or Block provider action turned on. Find that enabled rule and either disable it or turn the setting off, then re-check.
An action asks for approval but routes to no one: Edit the rule, add at least one approver, and save. The result should then name who must sign off.
An edit left the rule in an unexpected state: Open the rule's history, find the version that behaved correctly, and choose Roll back to this version, then re-check.
The result still says Not checked yet: Pick a scenario and select Check policy; the result only updates after a simulation runs.

Permissions

Anyone with Policy Studio access can run checks and read results; changing a rule's status, conditions, approvers, or rolling back a version needs an owner or admin.

Support

If a rule still will not behave after these steps, ask a workspace admin first. LumenReach support can help with policy behavior without accessing your private rule content.