Policy Runs

A policy run represents a single execution of a published policy.

Each run evaluates entities within the defined scope, applies rule conditions, and generates violations when defined criteria are met.

Navigate to Policy Runs

Go to:

Identity Governance & Administration > Policy > Policy Runs

The Policy Runs page provides execution history across all published policies.

Policy Runs List View

The list view provides visibility into:

• Run ID
• Policy name
• Policy type
• Run type
• Status
• Start time
• End time
• Evaluated entities
• Violations found
• Triggered by

Run Type

Run type indicates how execution was initiated:

• Manual – Triggered by an administrator
• Scheduled – Triggered by a configured schedule
• Event-based – Triggered by a system event

The list supports:

• Filtering by policy
• Filtering by status
• Filtering by run type
• Filtering by date range
• Column visibility control
• Column reordering
• Table density selection
• Refresh

Run Status

A policy run progresses through defined states:

Pending

Execution has been queued and is awaiting processing.

Running

Evaluation is currently in progress.

Completed

Evaluation completed successfully.

Completed with Errors

Evaluation completed, but partial failures occurred during processing.

Failed

Execution did not complete successfully.

All status changes are recorded for audit purposes.

View a Policy Run

To view run details:

1. Navigate to Identity Governance & Administration > Policy > Policy Runs.
2. Select the required run.

The run detail page displays:

• Execution metadata
• Scope evaluation summary
• Number of entities evaluated
• Violations generated
• Failure details (if applicable)

Each violation generated during the run is linked to its corresponding entity and violation record.

Computation and Remediation

Policy runs record the computation phase of policy evaluation.

During computation:

1. The configured scope is loaded.
2. Entities within scope are identified.
3. Rule conditions are evaluated.
4. Violations are created where conditions evaluate as true.

Remediation actions may execute asynchronously after violations are generated. Remediation processing does not delay completion of the computation phase.

Relationship to Violations

Each violation includes a reference to the Execution ID of the policy run in which it was created.

This linkage provides traceability between:

• Policy configuration
• Policy execution
• Violation creation
• Remediation activity

Policy Runs provide the execution-level view of governance enforcement across the system.