What causes CLUSTER_POLICY_NOT_FOUND?

A workspace admin deleted the policy that jobs or bundles reference. The job or bundle was migrated from another workspace and the policy ID does not exist in the new workspace. The policy ID in the job configuration was set manually and contains a typo. The policy was renamed or recreated with a new ID and job configurations were not updated

How do I fix CLUSTER_POLICY_NOT_FOUND?

Step 1: Run 'databricks cluster-policies list' via the CLI or navigate to Compute > Policies to list available policy IDs.. Step 2: Update the job definition or bundle YAML to reference a valid, existing policy ID.. Step 3: If the policy was deleted and needs to be recreated, ask a workspace admin to restore it with the same or equivalent rules.. Step 4: For bundles, update the policy_id in databricks.yml and run 'databricks bundle validate' before redeploying.. Step 5: After updating, trigger a manual run to confirm the cluster starts successfully.

High severityconfiguration

Power BI Refresh Error:
CLUSTER_POLICY_NOT_FOUND

What does this error mean?

A job, cluster creation request, or bundle deployment referenced a cluster policy ID that does not exist or has been deleted from the workspace.

Common causes

1A workspace admin deleted the policy that jobs or bundles reference
2The job or bundle was migrated from another workspace and the policy ID does not exist in the new workspace
3The policy ID in the job configuration was set manually and contains a typo
4The policy was renamed or recreated with a new ID and job configurations were not updated

How to fix it

1Step 1: Run 'databricks cluster-policies list' via the CLI or navigate to Compute > Policies to list available policy IDs.
2Step 2: Update the job definition or bundle YAML to reference a valid, existing policy ID.
3Step 3: If the policy was deleted and needs to be recreated, ask a workspace admin to restore it with the same or equivalent rules.
4Step 4: For bundles, update the policy_id in databricks.yml and run 'databricks bundle validate' before redeploying.
5Step 5: After updating, trigger a manual run to confirm the cluster starts successfully.

Frequently asked questions

Is a cluster policy required for all Databricks jobs?

No. Cluster policies are optional unless an admin has enforced policy usage through workspace settings. Without a policy, the default cluster configuration limits apply.

How do I find what policy ID was previously used?

Check the job's run history in the Databricks Jobs UI — the cluster spec is recorded per-run. Old run details show the policy_id that was used before the change.