<?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: Is there a way to let the DLT pipeline retry by itself? in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/is-there-a-way-to-let-the-dlt-pipeline-retry-by-itself/m-p/80674#M36116</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/109070"&gt;@guangyi&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;In DLT you have following two properties that you can set:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN class=""&gt;pipelines.maxFlowRetryAttempts&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Type:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;int&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;The maximum number of attempts to retry a flow before failing a pipeline update when a retryable failure occurs.&lt;/P&gt;&lt;P&gt;The default value is two. By default, when a retryable failure occurs, the Delta Live Tables runtime attempts to run the flow three times including the original attempt.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN class=""&gt;pipelines.numUpdateRetryAttempts&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Type:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;int&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;The maximum number of attempts to retry an update before failing the update when a retryable failure occurs. The retry is run as a full update.&lt;/P&gt;&lt;P&gt;The default is five. This parameter applies only to triggered updates run in production mode. There is no retry when your pipeline runs in development mode.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;You can also take a look on below answers:&lt;BR /&gt;&lt;BR /&gt;-&amp;nbsp;&lt;A href="https://community.databricks.com/t5/data-engineering/delta-live-tables-retry-on-failure/td-p/5926" target="_blank" rel="noopener"&gt;Delta Live Tables - RETRY_ON_FAILURE - Databricks Community - 5926&lt;/A&gt;&lt;/P&gt;&lt;P&gt;-&amp;nbsp;&lt;A href="https://community.databricks.com/t5/data-engineering/dlt-pipeline-retries/td-p/30388" target="_blank" rel="noopener"&gt;Solved: DLT Pipeline Retries - Databricks Community - 30388&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 26 Jul 2024 07:10:26 GMT</pubDate>
    <dc:creator>szymon_dybczak</dc:creator>
    <dc:date>2024-07-26T07:10:26Z</dc:date>
    <item>
      <title>Is there a way to let the DLT pipeline retry by itself?</title>
      <link>https://community.databricks.com/t5/data-engineering/is-there-a-way-to-let-the-dlt-pipeline-retry-by-itself/m-p/80658#M36108</link>
      <description>&lt;P&gt;&lt;SPAN&gt;I know I can make the workflow job retry automatically by adding following properties in the YAML file: max_retries or min_retry_interval_millis.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;However, I cannot find similar attributes in any DLT pipeline document. When I ask copilot it gives this answer:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot 2024-07-26 at 14.03.50.png" style="width: 488px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/9904i29A783758A5CAF91/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="Screenshot 2024-07-26 at 14.03.50.png" alt="Screenshot 2024-07-26 at 14.03.50.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I try to add these two attributes in the asset bundle YAML file. After deploying on the prod, I found these two properties actually added on the DLT pipeline setting &amp;gt; advanced &amp;gt; configuration section, but it still cannot retry automatically&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Is there a way to let the DLT retry by itself?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jul 2024 06:07:41 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/is-there-a-way-to-let-the-dlt-pipeline-retry-by-itself/m-p/80658#M36108</guid>
      <dc:creator>guangyi</dc:creator>
      <dc:date>2024-07-26T06:07:41Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a way to let the DLT pipeline retry by itself?</title>
      <link>https://community.databricks.com/t5/data-engineering/is-there-a-way-to-let-the-dlt-pipeline-retry-by-itself/m-p/80674#M36116</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/109070"&gt;@guangyi&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;In DLT you have following two properties that you can set:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN class=""&gt;pipelines.maxFlowRetryAttempts&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Type:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;int&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;The maximum number of attempts to retry a flow before failing a pipeline update when a retryable failure occurs.&lt;/P&gt;&lt;P&gt;The default value is two. By default, when a retryable failure occurs, the Delta Live Tables runtime attempts to run the flow three times including the original attempt.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN class=""&gt;pipelines.numUpdateRetryAttempts&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Type:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;int&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;The maximum number of attempts to retry an update before failing the update when a retryable failure occurs. The retry is run as a full update.&lt;/P&gt;&lt;P&gt;The default is five. This parameter applies only to triggered updates run in production mode. There is no retry when your pipeline runs in development mode.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;You can also take a look on below answers:&lt;BR /&gt;&lt;BR /&gt;-&amp;nbsp;&lt;A href="https://community.databricks.com/t5/data-engineering/delta-live-tables-retry-on-failure/td-p/5926" target="_blank" rel="noopener"&gt;Delta Live Tables - RETRY_ON_FAILURE - Databricks Community - 5926&lt;/A&gt;&lt;/P&gt;&lt;P&gt;-&amp;nbsp;&lt;A href="https://community.databricks.com/t5/data-engineering/dlt-pipeline-retries/td-p/30388" target="_blank" rel="noopener"&gt;Solved: DLT Pipeline Retries - Databricks Community - 30388&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jul 2024 07:10:26 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/is-there-a-way-to-let-the-dlt-pipeline-retry-by-itself/m-p/80674#M36116</guid>
      <dc:creator>szymon_dybczak</dc:creator>
      <dc:date>2024-07-26T07:10:26Z</dc:date>
    </item>
  </channel>
</rss>

