MetricSign
Start free
High severityfabricMicrosoft Fabric

Microsoft Fabric Error:
No Delta Transaction Log Entries Were Found

What does this error mean?

Fabric Lakehouse cannot read a directory as a Delta table because the _delta_log folder is missing or empty.

Common causes

  • 1Parquet files were copied directly to the table path (e.g., via azcopy or data pipeline) without converting them to Delta format
  • 2Attempting to query a folder created by a Spark write before the Delta format was enabled (plain Parquet output)
  • 3The _delta_log directory was accidentally deleted
  • 4Using spark.read.parquet() and then registering the result as a table without converting to Delta

How to fix it

  1. 1Convert existing Parquet files to Delta format: CONVERT TO DELTA parquet.`<abfss-path-to-folder>`.
  2. 2Alternatively, use Delta write mode from scratch: spark.read.parquet('<path>').write.format('delta').save('<new-path>').

Beyond the docs

Common practitioner solutions not covered in the official documentation.

  1. 1Verify the _delta_log directory exists in the table folder using the Lakehouse Explorer or an ABFSS ls command
  2. 2If the Delta log was accidentally deleted, restore it from the Recycle Bin in the Fabric portal if available
  3. 3When copying data into Lakehouse, always write via Delta API or pipeline Copy Data activity — avoid direct file copy to the Tables area

Frequently asked questions

Does this error affect Power BI reports in the same workspace?

Depends on the error type. Semantic model failures affect report freshness directly. Dataflow or pipeline failures may cascade into downstream semantic model failures.

How is debugging Fabric errors different from classic Power BI errors?

Fabric errors often require checking capacity utilization alongside the item-level error. The Fabric admin portal shows capacity pressure that Power BI Service doesn't expose.

Can Fabric errors be caused by capacity limits?

Yes — Fabric capacities have concurrent operation limits. An undersized capacity causes failures during peak usage.

Does this error appear in Power BI Desktop?

No — Fabric items are cloud-native. Desktop can connect to Fabric semantic models but cannot trigger or observe Fabric-specific errors.

Source · learn.microsoft.com/en-us/fabric/data-engineering/troubleshoot-lakehouse

Other fabric errors