What causes RESOURCE_ALREADY_EXISTS?

An idempotent pipeline or migration script does not use IF NOT EXISTS and is run more than once. Two concurrent job runs attempt to create the same managed Delta table or schema simultaneously. A Unity Catalog external location or storage credential name collides with an existing resource created by another workspace admin

How do I fix RESOURCE_ALREADY_EXISTS?

Step 1: Add IF NOT EXISTS to the CREATE statement (e.g., CREATE TABLE IF NOT EXISTS) or use CREATE OR REPLACE when the intent is to refresh the object.. Step 2: If the collision is from concurrent runs, add a job cluster lock or use a unique run-specific suffix for temporary objects.. Step 3: For Unity Catalog resources (external locations, credentials, catalogs), list existing objects with SHOW CATALOGS or the REST API before attempting creation.. Step 4: If the object is stale or from a failed previous run, DROP or clean it up first, then re-run the creation logic.

Medium severityconfiguration

Power BI Refresh Error:
RESOURCE_ALREADY_EXISTS

What does this error mean?

A create operation failed because an object — such as a catalog, schema, table, volume, or cluster policy — with the same name already exists in the target scope.

Common causes

1An idempotent pipeline or migration script does not use IF NOT EXISTS and is run more than once
2Two concurrent job runs attempt to create the same managed Delta table or schema simultaneously
3A Unity Catalog external location or storage credential name collides with an existing resource created by another workspace admin

How to fix it

1Step 1: Add IF NOT EXISTS to the CREATE statement (e.g., CREATE TABLE IF NOT EXISTS) or use CREATE OR REPLACE when the intent is to refresh the object.
2Step 2: If the collision is from concurrent runs, add a job cluster lock or use a unique run-specific suffix for temporary objects.
3Step 3: For Unity Catalog resources (external locations, credentials, catalogs), list existing objects with SHOW CATALOGS or the REST API before attempting creation.
4Step 4: If the object is stale or from a failed previous run, DROP or clean it up first, then re-run the creation logic.

Frequently asked questions

Does RESOURCE_ALREADY_EXISTS always mean a duplicate?

Usually yes, but it can also appear when a partially failed prior run left a half-created object. Always verify the object's state (e.g., DESCRIBE TABLE) before deciding to drop it.

How do I prevent this in pipeline code?

Use CREATE TABLE IF NOT EXISTS for Delta tables, and pattern your orchestration so that resource creation is only attempted once per logical lifecycle, or is wrapped in a try/except that ignores the 'already exists' case.