<?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: Retries not triggered for a Run Job task in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/retries-not-triggered-for-a-run-job-task/m-p/176644#M57186</link>
    <description>&lt;P&gt;Hi&amp;nbsp;@alejandorr&lt;/P&gt;&lt;P&gt;Yes, retries are supported on Run Job tasks. The Run Job task docs say to configure retries, run-duration or streaming-backlog thresholds, or notifications, see Advanced task settings, the same place you’d set them for a notebook task. So the setting itself isn’t the problem. &lt;SPAN&gt;&lt;A href="https://docs.databricks.com/aws/en/jobs/tasks/run-job" target="_blank" rel="noopener noreferrer"&gt;databricks&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;The clue is that the retry fields don’t show up in the Jobs API get response. That means they never reached the deployed job, so the parent task has no retry policy to apply. A few things to check:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Placement in the YAML:&amp;nbsp;max_retries and min_retry_interval_millis belong at the task level, as siblings of run_job_task. If they’re indented under run_job_task, they won’t be applied. It should look like this:&lt;/LI&gt;&lt;/OL&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;yaml&lt;/DIV&gt;&lt;DIV&gt;&lt;PRE&gt;&lt;SPAN&gt;resources:
  jobs:
    parent_job:
      name: parent-job
      tasks:
        - task_key: call_child
          max_retries: 3
          min_retry_interval_millis: 60000
          retry_on_timeout: false
          run_job_task:
            job_id: ${resources.jobs.child_job.id}&lt;/SPAN&gt;&lt;/PRE&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;OL&gt;&lt;LI&gt;Check what the bundle actually sends: Run databricks bundle validate --output json and look for max_retries on that task. If it’s missing there, the problem is in the YAML. Also confirm you deployed to the target you’re checking in the API.&lt;/LI&gt;&lt;LI&gt;Continuous trigger: If the parent job uses a continuous trigger, task retry policies don’t apply. Continuous jobs use their own retry mode with exponential backoff instead.&lt;/LI&gt;&lt;LI&gt;Isolate bundle vs. platform:&amp;nbsp;Add retries to the Run Job task by hand in the UI, then call the get API. If the fields show up, the platform supports it and the issue is in the bundle config.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;One design point to keep in mind: a retry on the Run Job task reruns the whole child job, including tasks that already succeeded. If only one task in the child job tends to fail, it’s often better to put retries on that task inside the child job, so only the failing work reruns.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 17 Nov 2026 10:30:23 GMT</pubDate>
    <dc:creator>ashishshivatare</dc:creator>
    <dc:date>2026-11-17T10:30:23Z</dc:date>
    <item>
      <title>Retries not triggered for a Run Job task</title>
      <link>https://community.databricks.com/t5/data-engineering/retries-not-triggered-for-a-run-job-task/m-p/176643#M57185</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Is it possible to configure retries for a Databricks task of type &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Run Job&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I configured &lt;/SPAN&gt;max_retries&lt;SPAN&gt; and &lt;/SPAN&gt;min_retry_interval_millis&lt;SPAN&gt; on the task in a Databricks Asset Bundle, as I would for a notebook task. However, when the called job fails, the Run Job task does not retry. Also, the retry fields do not appear in the Jobs API &lt;/SPAN&gt;get&lt;SPAN&gt; response.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Is this configuration supported for Run Job tasks? If so, how should retries be configured?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Nov 2026 10:15:17 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/retries-not-triggered-for-a-run-job-task/m-p/176643#M57185</guid>
      <dc:creator>alejandrorr</dc:creator>
      <dc:date>2026-11-17T10:15:17Z</dc:date>
    </item>
    <item>
      <title>Re: Retries not triggered for a Run Job task</title>
      <link>https://community.databricks.com/t5/data-engineering/retries-not-triggered-for-a-run-job-task/m-p/176644#M57186</link>
      <description>&lt;P&gt;Hi&amp;nbsp;@alejandorr&lt;/P&gt;&lt;P&gt;Yes, retries are supported on Run Job tasks. The Run Job task docs say to configure retries, run-duration or streaming-backlog thresholds, or notifications, see Advanced task settings, the same place you’d set them for a notebook task. So the setting itself isn’t the problem. &lt;SPAN&gt;&lt;A href="https://docs.databricks.com/aws/en/jobs/tasks/run-job" target="_blank" rel="noopener noreferrer"&gt;databricks&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;The clue is that the retry fields don’t show up in the Jobs API get response. That means they never reached the deployed job, so the parent task has no retry policy to apply. A few things to check:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Placement in the YAML:&amp;nbsp;max_retries and min_retry_interval_millis belong at the task level, as siblings of run_job_task. If they’re indented under run_job_task, they won’t be applied. It should look like this:&lt;/LI&gt;&lt;/OL&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;yaml&lt;/DIV&gt;&lt;DIV&gt;&lt;PRE&gt;&lt;SPAN&gt;resources:
  jobs:
    parent_job:
      name: parent-job
      tasks:
        - task_key: call_child
          max_retries: 3
          min_retry_interval_millis: 60000
          retry_on_timeout: false
          run_job_task:
            job_id: ${resources.jobs.child_job.id}&lt;/SPAN&gt;&lt;/PRE&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;OL&gt;&lt;LI&gt;Check what the bundle actually sends: Run databricks bundle validate --output json and look for max_retries on that task. If it’s missing there, the problem is in the YAML. Also confirm you deployed to the target you’re checking in the API.&lt;/LI&gt;&lt;LI&gt;Continuous trigger: If the parent job uses a continuous trigger, task retry policies don’t apply. Continuous jobs use their own retry mode with exponential backoff instead.&lt;/LI&gt;&lt;LI&gt;Isolate bundle vs. platform:&amp;nbsp;Add retries to the Run Job task by hand in the UI, then call the get API. If the fields show up, the platform supports it and the issue is in the bundle config.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;One design point to keep in mind: a retry on the Run Job task reruns the whole child job, including tasks that already succeeded. If only one task in the child job tends to fail, it’s often better to put retries on that task inside the child job, so only the failing work reruns.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Nov 2026 10:30:23 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/retries-not-triggered-for-a-run-job-task/m-p/176644#M57186</guid>
      <dc:creator>ashishshivatare</dc:creator>
      <dc:date>2026-11-17T10:30:23Z</dc:date>
    </item>
  </channel>
</rss>

