<?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: Massive Duplicate Alerts Auto‑Created by Git Folders After Recent Databricks Update in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/massive-duplicate-alerts-auto-created-by-git-folders-after/m-p/151863#M53718</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/222628"&gt;@kcheng&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Thanks for sharing the details. This looks like behaviour that will need workspace‑specific investigation by Databricks Support, rather than something the community can reliably diagnose or fix.&lt;/P&gt;
&lt;P&gt;Because it resulted in a sudden, large volume of auto‑created alerts, I’d strongly recommend raising a Support ticket with your workspace URL, region, and a rough time window when the alerts appeared. That will let the Support and engineering teams check backend logs, confirm whether this is expected behaviour, and advise on safe cleanup options.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="p1"&gt;&lt;FONT size="2" color="#FF6600"&gt;&lt;STRONG&gt;&lt;I&gt;If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.&lt;/I&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 24 Mar 2026 15:46:47 GMT</pubDate>
    <dc:creator>Ashwin_DSA</dc:creator>
    <dc:date>2026-03-24T15:46:47Z</dc:date>
    <item>
      <title>Massive Duplicate Alerts Auto‑Created by Git Folders After Recent Databricks Update</title>
      <link>https://community.databricks.com/t5/data-engineering/massive-duplicate-alerts-auto-created-by-git-folders-after/m-p/151836#M53715</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Hello Databricks Support Team,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;I’m experiencing a severe issue in my Databricks workspace related to the new Git‑Integrated Alerts behavior. Overnight, my workspace went from &lt;STRONG&gt;67 alerts&lt;/STRONG&gt; to &lt;STRONG&gt;nearly 1,000 alerts&lt;/STRONG&gt;, all of which appear to have been &lt;STRONG&gt;auto‑generated&lt;/STRONG&gt; from Git folders without any action taken on my part. Those hundreds of duplicate alerts are all marked as '&lt;STRONG&gt;Not Run&lt;/STRONG&gt;' and &lt;STRONG&gt;Stopped,&amp;nbsp;&lt;/STRONG&gt;and has&amp;nbsp;&lt;STRONG&gt;same name&lt;/STRONG&gt; as alerts stored in Git repositories. This behavior did &lt;STRONG&gt;not&lt;/STRONG&gt; exist as of Friday (March 21, 2026), but appeared suddenly the morning of &lt;STRONG&gt;March 23, 2026&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;This issue has severely impacted our alert management workflow since we created single Git folder for task separation and there's no option in workspace UI to disable Git-source alert syncing. This is extremely unintuitive and disruptive, and appears to have been triggered by a backend update rather than user action.&lt;/P&gt;&lt;P&gt;I would like to ask for answer on following request:&lt;/P&gt;&lt;DIV&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;Please confirm whether a recent Databricks update triggered Git folder alert syncing in our workspace.&lt;/STRONG&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Is there a feature flag or workspace configuration to disable Git‑integrated alert auto‑creation?&lt;/STRONG&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Guidance on safely cleaning up the hundreds of duplicate alerts created.&lt;/STRONG&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Would there be a feature 'Delete at Once' for user selected Alert?&lt;/STRONG&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;DIV&gt;&lt;P&gt;This issue severely affects usability for anyone using multiple Git repos inside a single Databricks workspace and seems inconsistent with typical alert management workflows.&lt;/P&gt;&lt;P&gt;We would appreciate your assistance in identifying the cause, disabling the behavior, and removing the auto‑generated alerts.&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 24 Mar 2026 13:53:34 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/massive-duplicate-alerts-auto-created-by-git-folders-after/m-p/151836#M53715</guid>
      <dc:creator>kcheng</dc:creator>
      <dc:date>2026-03-24T13:53:34Z</dc:date>
    </item>
    <item>
      <title>Re: Massive Duplicate Alerts Auto‑Created by Git Folders After Recent Databricks Update</title>
      <link>https://community.databricks.com/t5/data-engineering/massive-duplicate-alerts-auto-created-by-git-folders-after/m-p/151863#M53718</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/222628"&gt;@kcheng&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Thanks for sharing the details. This looks like behaviour that will need workspace‑specific investigation by Databricks Support, rather than something the community can reliably diagnose or fix.&lt;/P&gt;
&lt;P&gt;Because it resulted in a sudden, large volume of auto‑created alerts, I’d strongly recommend raising a Support ticket with your workspace URL, region, and a rough time window when the alerts appeared. That will let the Support and engineering teams check backend logs, confirm whether this is expected behaviour, and advise on safe cleanup options.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="p1"&gt;&lt;FONT size="2" color="#FF6600"&gt;&lt;STRONG&gt;&lt;I&gt;If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.&lt;/I&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 24 Mar 2026 15:46:47 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/massive-duplicate-alerts-auto-created-by-git-folders-after/m-p/151863#M53718</guid>
      <dc:creator>Ashwin_DSA</dc:creator>
      <dc:date>2026-03-24T15:46:47Z</dc:date>
    </item>
  </channel>
</rss>

