<?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 Issue with Disabled &amp;quot;Repair DAG&amp;quot;, &amp;quot;Repair All DAGs&amp;quot; Buttons in Airflow UI, functionality is working. in Get Started Discussions</title>
    <link>https://community.databricks.com/t5/get-started-discussions/issue-with-disabled-quot-repair-dag-quot-quot-repair-all-dags/m-p/116552#M9999</link>
    <description>&lt;P class=""&gt;We are encountering an issue in the Airflow UI where the 'Repair DAG' and 'Repair All DAGs' options are disabled when a specific task fails. While the repair functionality itself is working properly (i.e., the DAGs can still be repaired through execution), the UI is not reflecting this behavior as the buttons appear disabled. This issue occurs when using Databricks compute, where the integration with Databricks is managed through the Databricks Workflow Operator.&lt;/P&gt;&lt;P class=""&gt;This problem seems to be isolated to the UI interaction and does not affect the backend execution, which proceeds normally when attempting to repair failed tasks.&lt;/P&gt;</description>
    <pubDate>Fri, 25 Apr 2025 08:38:41 GMT</pubDate>
    <dc:creator>nachii_rajput</dc:creator>
    <dc:date>2025-04-25T08:38:41Z</dc:date>
    <item>
      <title>Issue with Disabled "Repair DAG", "Repair All DAGs" Buttons in Airflow UI, functionality is working.</title>
      <link>https://community.databricks.com/t5/get-started-discussions/issue-with-disabled-quot-repair-dag-quot-quot-repair-all-dags/m-p/116552#M9999</link>
      <description>&lt;P class=""&gt;We are encountering an issue in the Airflow UI where the 'Repair DAG' and 'Repair All DAGs' options are disabled when a specific task fails. While the repair functionality itself is working properly (i.e., the DAGs can still be repaired through execution), the UI is not reflecting this behavior as the buttons appear disabled. This issue occurs when using Databricks compute, where the integration with Databricks is managed through the Databricks Workflow Operator.&lt;/P&gt;&lt;P class=""&gt;This problem seems to be isolated to the UI interaction and does not affect the backend execution, which proceeds normally when attempting to repair failed tasks.&lt;/P&gt;</description>
      <pubDate>Fri, 25 Apr 2025 08:38:41 GMT</pubDate>
      <guid>https://community.databricks.com/t5/get-started-discussions/issue-with-disabled-quot-repair-dag-quot-quot-repair-all-dags/m-p/116552#M9999</guid>
      <dc:creator>nachii_rajput</dc:creator>
      <dc:date>2025-04-25T08:38:41Z</dc:date>
    </item>
    <item>
      <title>Re: Issue with Disabled "Repair DAG", "Repair All DAGs" Buttons in Airflow UI, f</title>
      <link>https://community.databricks.com/t5/get-started-discussions/issue-with-disabled-quot-repair-dag-quot-quot-repair-all-dags/m-p/139230#M11026</link>
      <description>&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;The issue with the 'Repair DAG' and 'Repair All DAGs' options being disabled in the Airflow UI when using the Databricks Workflow Operator is a known UI-specific problem that does not affect backend execution or the actual repair functionality. While tasks can be successfully repaired through workflow execution, the visual controls in the UI appear incorrectly disabled.​&lt;/P&gt;
&lt;H2 class="mb-2 mt-4 font-display font-semimedium text-base first:mt-0"&gt;Root Cause and Current State&lt;/H2&gt;
&lt;UL class="marker:text-quiet list-disc"&gt;
&lt;LI class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&amp;amp;&amp;gt;p]:pt-0 [&amp;amp;&amp;gt;p]:mb-2 [&amp;amp;&amp;gt;p]:my-0"&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;The backend repair functionalities, which rely on Airflow's integration with the Databricks API, continue to operate as expected, allowing DAGs and individual tasks to be repaired regardless of the UI state.​&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&amp;amp;&amp;gt;p]:pt-0 [&amp;amp;&amp;gt;p]:mb-2 [&amp;amp;&amp;gt;p]:my-0"&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;The cause of the visual issue appears to relate specifically to the way extra operator links (such as for repair actions) are surfaced and enabled in the Airflow UI for tasks that use custom Databricks integration classes, especially in newer provider versions or complex environments.​&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&amp;amp;&amp;gt;p]:pt-0 [&amp;amp;&amp;gt;p]:mb-2 [&amp;amp;&amp;gt;p]:my-0"&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;This issue is not unique to your setup and has surfaced for other users, suggesting a bug or missing UI state synchronization for these buttons when Databricks compute or operators are involved.​&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;H2 class="mb-2 mt-4 font-display font-semimedium text-base first:mt-0"&gt;Possible Remediation and Best Practices&lt;/H2&gt;
&lt;UL class="marker:text-quiet list-disc"&gt;
&lt;LI class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&amp;amp;&amp;gt;p]:pt-0 [&amp;amp;&amp;gt;p]:mb-2 [&amp;amp;&amp;gt;p]:my-0"&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;Ensure you are running the latest version of both Airflow and the apache-airflow-providers-databricks package, as several bugs related to Databricks repair and UI actions have been addressed in recent releases.​&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&amp;amp;&amp;gt;p]:pt-0 [&amp;amp;&amp;gt;p]:mb-2 [&amp;amp;&amp;gt;p]:my-0"&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;Review whether your Databricks connection and job/task parameters are correctly surfaced to the UI—missing run identifiers, connection IDs, or improper task states may lead to UI links being disabled.​&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&amp;amp;&amp;gt;p]:pt-0 [&amp;amp;&amp;gt;p]:mb-2 [&amp;amp;&amp;gt;p]:my-0"&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;If you need immediate access to these options, you can continue to trigger repairs via direct API calls, backend scripts, or through the Databricks UI, as the backend is not impacted.​&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;H2 class="mb-2 mt-4 font-display font-semimedium text-base first:mt-0"&gt;Additional Notes&lt;/H2&gt;
&lt;UL class="marker:text-quiet list-disc"&gt;
&lt;LI class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&amp;amp;&amp;gt;p]:pt-0 [&amp;amp;&amp;gt;p]:mb-2 [&amp;amp;&amp;gt;p]:my-0"&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;Monitor the Airflow and Databricks provider changelogs for further fixes to UI-related issues. Specifically, bugs related to "repair buttons not overriding template parameters" and UI state have been patched as recently as late 2025.​&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&amp;amp;&amp;gt;p]:pt-0 [&amp;amp;&amp;gt;p]:mb-2 [&amp;amp;&amp;gt;p]:my-0"&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;If running Airflow 2.x or an older provider, consider upgrading because some operator link behaviors (such as repair all failed tasks) are handled differently in Airflow 3.x and in new Databricks provider releases.​&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;In summary, the disabled repair options in the UI are a frontend problem impacting user interaction but do not prevent actual job repair through Airflow or Databricks API calls. Keeping your environment updated is the best path toward a fix, but repairs can proceed through backend paths until an official UI update resolvesolves the issue&lt;/P&gt;</description>
      <pubDate>Sun, 16 Nov 2025 17:17:52 GMT</pubDate>
      <guid>https://community.databricks.com/t5/get-started-discussions/issue-with-disabled-quot-repair-dag-quot-quot-repair-all-dags/m-p/139230#M11026</guid>
      <dc:creator>mark_ott</dc:creator>
      <dc:date>2025-11-16T17:17:52Z</dc:date>
    </item>
  </channel>
</rss>

