Lineage view shows different patterns depending on order of Lakehouse to Dataflow creation

The lineage view currently shows different relationships between the Gen2 Dataflow source and Lakehouse when created in different orders:

• When the Gen2 Dataflow is created first, the Lakehouse the lineage view will show the full singular path from source (dataflow) to the Lakehouse and the SQL analytics endpoint and model (see diagram #1 in forum link below)
• When the Lakehouse is created first, and the source for the Lakehouse using a Gen2 Dataflow is created together from within the Lakehouse, the lineage view will show a broken chain with the SQL Server/Lakehouse to Dataflow in one batch, and the Lakehouse to SQL analytics endpoint/model in another batch. There is no relationship drawn from the Dataflow to the Lakehouses SQL analytics endpoint/model, which is strange. Nor can you see the name of the Lakehouse connected to the Dataflow in the first batch (see diagram #2 in forum link below).
• See diagrams in linked Forum discussion:

It would be good if the lineage view always showed the full chain relationship (as in #1).