Direct Lake: pipeline refresh in parallel with notebook write, data not updated

Hi davidjmpinto,

Your thread on the same setup in the Desktop forum has an accepted answer: Direct Lake auto update with parallel refresh in a composite model. For the questions here, the short version:

• A Direct Lake table only shows the Delta version it was last framed on. A framing that runs before the notebook's commit is visible pins the old version and still reports success, so you get no error.
• Automatic updates do reframe after a new commit, but you don't control when, and with a refresh running on the same model at the same moment you can't rely on the order.
• So don't run both on the same model in parallel. Run the semantic model refresh once, after both the copy job and the notebook have succeeded. In a composite model that one refresh reloads the import tables and reframes the Direct Lake tables in the same operation.
• If the report should only change when the whole load is done, also turn off "Keep your Direct Lake data up to date", so the pipeline's refresh is the only thing that reframes.

The copy job and the notebook can keep running in parallel. Only the refresh has to wait for both.