https://community.databricks.com/t5/community-articles/solving-the-quot-untitled-quot-lineage-mystery-in-unity-catalog/m-p/158322#M1235 <P>Hey everyone,</P><P>Have you ever opened Databricks Catalog Explorer to audit a table, only to find the downstream job listed as <STRONG>"Untitled"</STRONG>? Databricks Unity Catalog is incredibly powerful for automated lineage, but it quietly breaks the moment you orchestrate pipelines using <FONT face="mingliu,biaukai" color="#993300">dbutils.notebook.run()</FONT>. Because the platform executes child notebooks in an isolated, temporary "instance run" rather than the parent job run context, the link back to your scheduled workflow completely vanishes.</P><P>If this silent lineage gap is making production debugging a headache for your team, I just published a short write-up on how to easily fix it. By capturing the parent Job ID and passing it down into Delta’s <FONT face="ms pmincho,hiragino mincho pron" color="#993300">userMetadata </FONT>configuration, you can embed a permanent audit trail directly into your table transaction logs.</P><P>Check out the quick step-by-step implementation and code snippets over on Medium: <A class="" href="https://medium.com/stackademic/the-hidden-lineage-in-databricks-the-mystery-behind-untitled-lineage-entries-ecc7b678df5d" target="_blank" rel="noopener">The Hidden Lineage in Databricks: The Mystery Behind “Untitled” Lineage Entries</A>.</P> Thu, 04 Jun 2026 16:43:09 GMT Avinash_Narala 2026-06-04T16:43:09Z https://community.databricks.com/t5/community-articles/solving-the-quot-untitled-quot-lineage-mystery-in-unity-catalog/m-p/158322#M1235 <P>Hey everyone,</P><P>Have you ever opened Databricks Catalog Explorer to audit a table, only to find the downstream job listed as <STRONG>"Untitled"</STRONG>? Databricks Unity Catalog is incredibly powerful for automated lineage, but it quietly breaks the moment you orchestrate pipelines using <FONT face="mingliu,biaukai" color="#993300">dbutils.notebook.run()</FONT>. Because the platform executes child notebooks in an isolated, temporary "instance run" rather than the parent job run context, the link back to your scheduled workflow completely vanishes.</P><P>If this silent lineage gap is making production debugging a headache for your team, I just published a short write-up on how to easily fix it. By capturing the parent Job ID and passing it down into Delta’s <FONT face="ms pmincho,hiragino mincho pron" color="#993300">userMetadata </FONT>configuration, you can embed a permanent audit trail directly into your table transaction logs.</P><P>Check out the quick step-by-step implementation and code snippets over on Medium: <A class="" href="https://medium.com/stackademic/the-hidden-lineage-in-databricks-the-mystery-behind-untitled-lineage-entries-ecc7b678df5d" target="_blank" rel="noopener">The Hidden Lineage in Databricks: The Mystery Behind “Untitled” Lineage Entries</A>.</P> Thu, 04 Jun 2026 16:43:09 GMT https://community.databricks.com/t5/community-articles/solving-the-quot-untitled-quot-lineage-mystery-in-unity-catalog/m-p/158322#M1235 Avinash_Narala 2026-06-04T16:43:09Z