Composite model: Direct Lake auto-update + parallel refresh, no errors but stale data

Hi,

Yes, this can happen if the Direct Lake tables are reframed before the notebook finishes writing the latest Delta changes. A successful semantic model refresh does not necessarily mean the Direct Lake tables are using the latest data.

I’d recommend running the notebook first and triggering the semantic model refresh only after the Delta writes have completed. This avoids a timing issue between the two operations.

Also, check whether the report is using the expected Direct Lake tables and whether fallback to DirectQuery is occurring. If the issue persists, test with a refresh after the notebook completes and compare the results.

I would not assume this is a confirmed platform limitation without further testing, but sequential execution is the safer approach for this pipeline.

Hope this Helps!

Thanks