<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Notebook runs not found due to retention limits with dbutils.notebook.run in Administration &amp; Architecture</title>
    <link>https://community.databricks.com/t5/administration-architecture/notebook-runs-not-found-due-to-retention-limits-with-dbutils/m-p/112850#M3137</link>
    <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/23951"&gt;@ErikApption&lt;/a&gt;&amp;nbsp;,&lt;BR /&gt;&lt;BR /&gt;Maybe I am wrong but I will give you my opinion.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P class=""&gt;Each time you execute dbutils.notebook.run(), it launches a new and independent execution within the same cluster&lt;SPAN class=""&gt;. So, if you run the cell today and then run it again tomorrow, there should be &lt;/SPAN&gt;two separate ephemeral executions&lt;SPAN class=""&gt;.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;However, the issue is that &lt;/SPAN&gt;&lt;STRONG&gt;Databricks does not treat these as persistent jobs&lt;SPAN class=""&gt;—they are &lt;/SPAN&gt;temporary executions&lt;SPAN class=""&gt; that &lt;/SPAN&gt;are not stored permanently&lt;/STRONG&gt;&lt;SPAN class=""&gt;.&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;STRONG&gt;Databricks automatically deletes old executions&lt;/STRONG&gt;&lt;/P&gt;&lt;P class=""&gt;•Even though new executions are created each time you run the notebook, &lt;SPAN class=""&gt;Databricks automatically deletes old executions&lt;/SPAN&gt; based on its retention policies.&lt;BR /&gt;•If a process tries to access a past execution that has already been deleted, the error &lt;SPAN class=""&gt;“Notebook runs not found due to retention limits”&lt;/SPAN&gt; will appear.&lt;/P&gt;&lt;P class=""&gt;&lt;STRONG&gt;Timeout or Expiry Constraints&lt;/STRONG&gt;&lt;/P&gt;&lt;P class=""&gt;•&lt;SPAN class=""&gt;dbutils.notebook.run()&lt;/SPAN&gt; allows a &lt;SPAN class=""&gt;timeout_seconds&lt;/SPAN&gt; parameter, but if &lt;SPAN class=""&gt;Databricks is down for more than 10 minutes&lt;/SPAN&gt;, the run fails regardless of timeout settings&lt;BR /&gt;•&lt;SPAN class=""&gt;If no timeout is set (timeout_seconds=0)&lt;/SPAN&gt;, the notebook must still complete within &lt;SPAN class=""&gt;30 days&lt;/SPAN&gt;, otherwise, it gets removed.&lt;/P&gt;&lt;P class=""&gt;&lt;STRONG&gt;Job Execution History Not Tracked&lt;BR /&gt;&lt;/STRONG&gt;&lt;SPAN class=""&gt;• Unlike standard &lt;/SPAN&gt;Databricks Jobs&lt;SPAN class=""&gt;, which persist in the Jobs UI, &lt;/SPAN&gt;notebook runs triggered via dbutils.notebook.run() do not retain long-term execution logs&lt;SPAN class=""&gt;.&lt;BR /&gt;&lt;/SPAN&gt;•Once the metadata is deleted, Databricks can no longer retrieve details about past executions, leading to this error.&lt;BR /&gt;&lt;BR /&gt;Hope have given you an idea &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;Isi&lt;/P&gt;</description>
    <pubDate>Mon, 17 Mar 2025 21:27:10 GMT</pubDate>
    <dc:creator>Isi</dc:creator>
    <dc:date>2025-03-17T21:27:10Z</dc:date>
    <item>
      <title>Notebook runs not found due to retention limits with dbutils.notebook.run</title>
      <link>https://community.databricks.com/t5/administration-architecture/notebook-runs-not-found-due-to-retention-limits-with-dbutils/m-p/112637#M3126</link>
      <description>&lt;P&gt;We saw this odd error in an AWS deployment, we have one notebook calling another one through&lt;/P&gt;&lt;PRE&gt; dbutils.notebook.run(...) &lt;/PRE&gt;&lt;P&gt;and this suddenly stopped working and failed with "&lt;STRONG&gt;&lt;EM&gt;Notebook runs not found due to retention limits&lt;/EM&gt;&lt;/STRONG&gt;",&amp;nbsp;the "learn more" points to&amp;nbsp;&lt;A href="https://docs.databricks.com/aws/en/jobs/monitor#view-runs-for-a-job" target="_blank"&gt;Databricks Documentation&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Any clues what can be causing this and how to fix it?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 14 Mar 2025 18:34:53 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/notebook-runs-not-found-due-to-retention-limits-with-dbutils/m-p/112637#M3126</guid>
      <dc:creator>ErikApption</dc:creator>
      <dc:date>2025-03-14T18:34:53Z</dc:date>
    </item>
    <item>
      <title>Re: Notebook runs not found due to retention limits with dbutils.notebook.run</title>
      <link>https://community.databricks.com/t5/administration-architecture/notebook-runs-not-found-due-to-retention-limits-with-dbutils/m-p/112850#M3137</link>
      <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/23951"&gt;@ErikApption&lt;/a&gt;&amp;nbsp;,&lt;BR /&gt;&lt;BR /&gt;Maybe I am wrong but I will give you my opinion.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P class=""&gt;Each time you execute dbutils.notebook.run(), it launches a new and independent execution within the same cluster&lt;SPAN class=""&gt;. So, if you run the cell today and then run it again tomorrow, there should be &lt;/SPAN&gt;two separate ephemeral executions&lt;SPAN class=""&gt;.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;However, the issue is that &lt;/SPAN&gt;&lt;STRONG&gt;Databricks does not treat these as persistent jobs&lt;SPAN class=""&gt;—they are &lt;/SPAN&gt;temporary executions&lt;SPAN class=""&gt; that &lt;/SPAN&gt;are not stored permanently&lt;/STRONG&gt;&lt;SPAN class=""&gt;.&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;STRONG&gt;Databricks automatically deletes old executions&lt;/STRONG&gt;&lt;/P&gt;&lt;P class=""&gt;•Even though new executions are created each time you run the notebook, &lt;SPAN class=""&gt;Databricks automatically deletes old executions&lt;/SPAN&gt; based on its retention policies.&lt;BR /&gt;•If a process tries to access a past execution that has already been deleted, the error &lt;SPAN class=""&gt;“Notebook runs not found due to retention limits”&lt;/SPAN&gt; will appear.&lt;/P&gt;&lt;P class=""&gt;&lt;STRONG&gt;Timeout or Expiry Constraints&lt;/STRONG&gt;&lt;/P&gt;&lt;P class=""&gt;•&lt;SPAN class=""&gt;dbutils.notebook.run()&lt;/SPAN&gt; allows a &lt;SPAN class=""&gt;timeout_seconds&lt;/SPAN&gt; parameter, but if &lt;SPAN class=""&gt;Databricks is down for more than 10 minutes&lt;/SPAN&gt;, the run fails regardless of timeout settings&lt;BR /&gt;•&lt;SPAN class=""&gt;If no timeout is set (timeout_seconds=0)&lt;/SPAN&gt;, the notebook must still complete within &lt;SPAN class=""&gt;30 days&lt;/SPAN&gt;, otherwise, it gets removed.&lt;/P&gt;&lt;P class=""&gt;&lt;STRONG&gt;Job Execution History Not Tracked&lt;BR /&gt;&lt;/STRONG&gt;&lt;SPAN class=""&gt;• Unlike standard &lt;/SPAN&gt;Databricks Jobs&lt;SPAN class=""&gt;, which persist in the Jobs UI, &lt;/SPAN&gt;notebook runs triggered via dbutils.notebook.run() do not retain long-term execution logs&lt;SPAN class=""&gt;.&lt;BR /&gt;&lt;/SPAN&gt;•Once the metadata is deleted, Databricks can no longer retrieve details about past executions, leading to this error.&lt;BR /&gt;&lt;BR /&gt;Hope have given you an idea &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;Isi&lt;/P&gt;</description>
      <pubDate>Mon, 17 Mar 2025 21:27:10 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/notebook-runs-not-found-due-to-retention-limits-with-dbutils/m-p/112850#M3137</guid>
      <dc:creator>Isi</dc:creator>
      <dc:date>2025-03-17T21:27:10Z</dc:date>
    </item>
  </channel>
</rss>

