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

Hi davidjmpinto,

Same setup as your other two threads, so in short (the details and the accepted answer are in Direct Lake auto update with parallel refresh in a composite model):

• Yes, the Direct Lake tables can end up on an older Delta version without any error. A framing only sees the commits that are visible when it runs, and a successful refresh doesn't check whether newer data landed just after.
• You can't rely on the order when a pipeline refresh and automatic updates run on the same model at the same time. Run one semantic model refresh after both the copy job and the notebook have succeeded. In a composite model that single refresh loads the import tables and reframes the Direct Lake tables together.
• If the report should only change when the whole load is done, turn off "Keep your Direct Lake data up to date" so the pipeline is the only thing that reframes.