Medium severityfabric
Power BI Refresh Error:
Table Was Not Found in Lakehouse
What does this error mean?
A SQL query or Spark command references a table that does not exist in the Fabric Lakehouse metadata catalog. Delta Lake table names are case-sensitive, so a casing mismatch or a reference to a table that was dropped, renamed, or never created all produce this error.
Common causes
- 1Table name in the query has incorrect casing or spelling (Delta Lake is case-sensitive)
- 2The table was dropped or renamed after the query was written
- 3Referencing a table in a different lakehouse or workspace without using a fully qualified name
- 4A pipeline that creates the table has not run yet, or failed before creating the table
- 5Using a shortcut that points to a path that no longer exists or was moved
How to fix it
- 1Run SHOW TABLES IN <schema> or browse the Lakehouse Explorer to confirm the table name and its exact casing
- 2If the table was renamed, update the query or pipeline to use the new name
- 3If accessing a table in another lakehouse, use the fully qualified format: <workspace>.<lakehouse>.<schema>.<table>
Beyond the docs
Common practitioner solutions not covered in the official documentation.
- 1Check that the pipeline or notebook that creates the table ran successfully before this query executes
- 2If using a shortcut, verify the shortcut target path is valid and the source data still exists
Official documentation: https://learn.microsoft.com/en-us/fabric/data-engineering/troubleshoot-lakehouse