<?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 Notifications for scheduled refreshes - now in Beta in Community Articles</title>
    <link>https://community.databricks.com/t5/community-articles/notifications-for-scheduled-refreshes-now-in-beta/m-p/153600#M1135</link>
    <description>&lt;P&gt;&lt;SPAN&gt;If you’ve ever worked with scheduled refreshes for Materialized Views or Streaming Tables, you probably know this pain. If your DDL-scheduled MV or ST refresh failed, nothing happened. No email, no alert, no indication that your data was stale (until you get pinged about stale data or increased costs).&lt;/SPAN&gt; &lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;That’s now changing. Databricks just introduced failure notifications for scheduled refreshes (Beta).&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;You can now configure email alerts for when refreshes start, succeed, or fail directly from the Catalog Explorer.&lt;/SPAN&gt; &lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;span class="lia-unicode-emoji" title=":paperclip:"&gt;📎&lt;/span&gt; Bonus: Notification emails include a direct link to the run history - making debugging much faster&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="schedules_100.png" style="width: 999px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/25732i429E48BBF8A6A2F0/image-size/large?v=v2&amp;amp;px=999" role="button" title="schedules_100.png" alt="schedules_100.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 07 Apr 2026 07:43:11 GMT</pubDate>
    <dc:creator>szymon_dybczak</dc:creator>
    <dc:date>2026-04-07T07:43:11Z</dc:date>
    <item>
      <title>Notifications for scheduled refreshes - now in Beta</title>
      <link>https://community.databricks.com/t5/community-articles/notifications-for-scheduled-refreshes-now-in-beta/m-p/153600#M1135</link>
      <description>&lt;P&gt;&lt;SPAN&gt;If you’ve ever worked with scheduled refreshes for Materialized Views or Streaming Tables, you probably know this pain. If your DDL-scheduled MV or ST refresh failed, nothing happened. No email, no alert, no indication that your data was stale (until you get pinged about stale data or increased costs).&lt;/SPAN&gt; &lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;That’s now changing. Databricks just introduced failure notifications for scheduled refreshes (Beta).&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;You can now configure email alerts for when refreshes start, succeed, or fail directly from the Catalog Explorer.&lt;/SPAN&gt; &lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;span class="lia-unicode-emoji" title=":paperclip:"&gt;📎&lt;/span&gt; Bonus: Notification emails include a direct link to the run history - making debugging much faster&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="schedules_100.png" style="width: 999px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/25732i429E48BBF8A6A2F0/image-size/large?v=v2&amp;amp;px=999" role="button" title="schedules_100.png" alt="schedules_100.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Apr 2026 07:43:11 GMT</pubDate>
      <guid>https://community.databricks.com/t5/community-articles/notifications-for-scheduled-refreshes-now-in-beta/m-p/153600#M1135</guid>
      <dc:creator>szymon_dybczak</dc:creator>
      <dc:date>2026-04-07T07:43:11Z</dc:date>
    </item>
    <item>
      <title>Re: Notifications for scheduled refreshes - now in Beta</title>
      <link>https://community.databricks.com/t5/community-articles/notifications-for-scheduled-refreshes-now-in-beta/m-p/153615#M1136</link>
      <description>&lt;P&gt;Welcome back,&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/110502"&gt;@szymon_dybczak&lt;/a&gt;!&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":grinning_face_with_big_eyes:"&gt;😃&lt;/span&gt;&lt;BR /&gt;That silent failure pain was real. These alerts are a massive win for everyone’s sanity. Thanks for the heads-up!&lt;/P&gt;</description>
      <pubDate>Tue, 07 Apr 2026 12:06:59 GMT</pubDate>
      <guid>https://community.databricks.com/t5/community-articles/notifications-for-scheduled-refreshes-now-in-beta/m-p/153615#M1136</guid>
      <dc:creator>Advika</dc:creator>
      <dc:date>2026-04-07T12:06:59Z</dc:date>
    </item>
    <item>
      <title>Re: Notifications for scheduled refreshes - now in Beta</title>
      <link>https://community.databricks.com/t5/community-articles/notifications-for-scheduled-refreshes-now-in-beta/m-p/153643#M1137</link>
      <description>&lt;P&gt;Thanks &lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/152834"&gt;@Advika&lt;/a&gt;&amp;nbsp;! Yes, I'm back -three weeks in South America have been great :D. And that’s a great feature indeed &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Apr 2026 16:51:24 GMT</pubDate>
      <guid>https://community.databricks.com/t5/community-articles/notifications-for-scheduled-refreshes-now-in-beta/m-p/153643#M1137</guid>
      <dc:creator>szymon_dybczak</dc:creator>
      <dc:date>2026-04-07T16:51:24Z</dc:date>
    </item>
  </channel>
</rss>

