<?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: Repairing job is useful but disabled if the job is triggered by another Run job task in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/repairing-job-is-useful-but-disabled-if-the-job-is-triggered-by/m-p/110964#M43751</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/150320"&gt;@carolsun08&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How are you doing today?,&amp;nbsp;Yeah, it's a bit frustrating that the repair job option is disabled when running jobs through Job Run tasks in an orchestration job. While there's no official confirmation on when this might change, it would definitely be a helpful improvement. You might want to share this as feedback on Databricks forums or check their roadmap for updates. In the meantime, restructuring the job so individual tasks can be retried separately could be a workaround. Hopefully, they make this more flexible soon!&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Brahma&lt;/P&gt;</description>
    <pubDate>Sat, 22 Feb 2025 16:24:30 GMT</pubDate>
    <dc:creator>Brahmareddy</dc:creator>
    <dc:date>2025-02-22T16:24:30Z</dc:date>
    <item>
      <title>Repairing job is useful but disabled if the job is triggered by another Run job task</title>
      <link>https://community.databricks.com/t5/data-engineering/repairing-job-is-useful-but-disabled-if-the-job-is-triggered-by/m-p/110958#M43750</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I regularly use the repair job option to rerun a subset of a larger data pipeline job. However, this option is disabled if I start this job from another "orchestration job" via Job Run tasks. The "repair" button is disabled in my case. This restriction causes my to rerun the whole job again and it is inefficient. Is it in the roadmap to enable the repair feature for this case?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 22 Feb 2025 13:05:43 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/repairing-job-is-useful-but-disabled-if-the-job-is-triggered-by/m-p/110958#M43750</guid>
      <dc:creator>carolsun08</dc:creator>
      <dc:date>2025-02-22T13:05:43Z</dc:date>
    </item>
    <item>
      <title>Re: Repairing job is useful but disabled if the job is triggered by another Run job task</title>
      <link>https://community.databricks.com/t5/data-engineering/repairing-job-is-useful-but-disabled-if-the-job-is-triggered-by/m-p/110964#M43751</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/150320"&gt;@carolsun08&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How are you doing today?,&amp;nbsp;Yeah, it's a bit frustrating that the repair job option is disabled when running jobs through Job Run tasks in an orchestration job. While there's no official confirmation on when this might change, it would definitely be a helpful improvement. You might want to share this as feedback on Databricks forums or check their roadmap for updates. In the meantime, restructuring the job so individual tasks can be retried separately could be a workaround. Hopefully, they make this more flexible soon!&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Brahma&lt;/P&gt;</description>
      <pubDate>Sat, 22 Feb 2025 16:24:30 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/repairing-job-is-useful-but-disabled-if-the-job-is-triggered-by/m-p/110964#M43751</guid>
      <dc:creator>Brahmareddy</dc:creator>
      <dc:date>2025-02-22T16:24:30Z</dc:date>
    </item>
    <item>
      <title>Re: Repairing job is useful but disabled if the job is triggered by another Run job task</title>
      <link>https://community.databricks.com/t5/data-engineering/repairing-job-is-useful-but-disabled-if-the-job-is-triggered-by/m-p/140068#M51341</link>
      <description>&lt;P&gt;What is the point of copy-pasting an LLM response that doesn't answer the question, and ignores the context that they are already sharing this on the Databricks forum?&lt;/P&gt;</description>
      <pubDate>Mon, 24 Nov 2025 09:22:38 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/repairing-job-is-useful-but-disabled-if-the-job-is-triggered-by/m-p/140068#M51341</guid>
      <dc:creator>bkapers</dc:creator>
      <dc:date>2025-11-24T09:22:38Z</dc:date>
    </item>
  </channel>
</rss>

