What causes RESOURCE_DOES_NOT_EXIST?

A job is configured to run on an existing cluster whose ID was deleted or rotated during infrastructure changes. An API call references a job ID, run ID, or cluster policy ID that no longer exists in the workspace. A Unity Catalog managed table's backing storage location was removed outside of Databricks, causing the catalog entry to become a dangling reference

How do I fix RESOURCE_DOES_NOT_EXIST?

Step 1: Note the resource type and ID from the error message, then verify existence via the Databricks UI or REST API (GET /api/2.1/jobs/get?job_id=...).. Step 2: If the cluster or pool was deleted, update the job definition to point to a new or existing compute resource.. Step 3: For Unity Catalog managed tables with missing storage, run DESCRIBE EXTENDED on the table and compare the storage location to what exists in the cloud bucket.. Step 4: Re-create the missing resource if intentional, or update all references to point to the correct replacement.

High severityconfiguration

Power BI Refresh Error:
RESOURCE_DOES_NOT_EXIST

What does this error mean?

An API call or SQL statement referenced a Databricks resource — such as a cluster, job, instance pool, or Unity Catalog object — that cannot be found, typically because it was deleted or never created.

Common causes

1A job is configured to run on an existing cluster whose ID was deleted or rotated during infrastructure changes
2An API call references a job ID, run ID, or cluster policy ID that no longer exists in the workspace
3A Unity Catalog managed table's backing storage location was removed outside of Databricks, causing the catalog entry to become a dangling reference

How to fix it

1Step 1: Note the resource type and ID from the error message, then verify existence via the Databricks UI or REST API (GET /api/2.1/jobs/get?job_id=...).
2Step 2: If the cluster or pool was deleted, update the job definition to point to a new or existing compute resource.
3Step 3: For Unity Catalog managed tables with missing storage, run DESCRIBE EXTENDED on the table and compare the storage location to what exists in the cloud bucket.
4Step 4: Re-create the missing resource if intentional, or update all references to point to the correct replacement.

Frequently asked questions

How is this different from TABLE_OR_VIEW_NOT_FOUND?

TABLE_OR_VIEW_NOT_FOUND is a SQL-level error for missing relations in a query. RESOURCE_DOES_NOT_EXIST is a REST API or system-level error for missing compute or catalog infrastructure resources.

Can this happen after a workspace migration?

Yes. Workspace migrations and Unity Catalog upgrades frequently change resource IDs. All job definitions and API clients that reference hard-coded IDs must be updated after a migration.