What causes DELTA_TABLE_NOT_FOUND?

The table name or path in the notebook or job has a typo or wrong database/schema prefix. The table was dropped by another job or by a DROP TABLE statement. The Delta table was created in a different catalog or schema than the job is reading from. The _delta_log directory is missing because the path points to raw files rather than a registered Delta table. A Unity Catalog table was deleted or the external location was removed

How do I fix DELTA_TABLE_NOT_FOUND?

Run `SHOW TABLES IN ` or `DESCRIBE DETAIL ` to confirm the table exists and is accessible.. Check for typos in the table name, schema, and catalog — Unity Catalog uses three-part names: `catalog.schema.table`.. If the table was accidentally dropped, restore it from Delta time travel if within the retention window: `CREATE TABLE ... AS SELECT * FROM delta.\` \` VERSION AS OF `.. Verify the cluster or job principal has `USE SCHEMA` and `SELECT` privileges on the containing schema.. If pointing to a path, confirm the path contains a `_delta_log` directory — otherwise it is not a Delta table.

High severitysql

Power BI Refresh Error:
DELTA_TABLE_NOT_FOUND

What does this error mean?

The specified Delta table could not be found. Either the table does not exist in the Unity Catalog or Hive metastore, or the path provided does not contain a valid Delta table.

Common causes

1The table name or path in the notebook or job has a typo or wrong database/schema prefix
2The table was dropped by another job or by a DROP TABLE statement
3The Delta table was created in a different catalog or schema than the job is reading from
4The _delta_log directory is missing because the path points to raw files rather than a registered Delta table
5A Unity Catalog table was deleted or the external location was removed

How to fix it

1Run `SHOW TABLES IN <schema>` or `DESCRIBE DETAIL <table_name>` to confirm the table exists and is accessible.
2Check for typos in the table name, schema, and catalog — Unity Catalog uses three-part names: `catalog.schema.table`.
3If the table was accidentally dropped, restore it from Delta time travel if within the retention window: `CREATE TABLE ... AS SELECT * FROM delta.\`<path>\` VERSION AS OF <n>`.
4Verify the cluster or job principal has `USE SCHEMA` and `SELECT` privileges on the containing schema.
5If pointing to a path, confirm the path contains a `_delta_log` directory — otherwise it is not a Delta table.

Frequently asked questions

Can I recover a dropped Delta table without a backup?

Yes, if the data files and _delta_log still exist on storage within the retention period. Use `CREATE TABLE ... LOCATION '<path>'` to re-register the table and it will pick up the existing Delta log.