<?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: Lakeflow jobs file trigger thru overwritten files in Get Started Discussions</title>
    <link>https://community.databricks.com/t5/get-started-discussions/lakeflow-jobs-file-trigger-thru-overwritten-files/m-p/155640#M11723</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/216690"&gt;@Ashwin_DSA&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;Btw, my trigger is pointed to a root path already. My goal is to reprocess any file (if they reupload the raw file again because of some fixes to the data). It's possible with autoloader (reprocess overwritten files), but my problem is how I will automatically trigger the job.&lt;/P&gt;</description>
    <pubDate>Tue, 28 Apr 2026 06:57:43 GMT</pubDate>
    <dc:creator>DazzaiDe</dc:creator>
    <dc:date>2026-04-28T06:57:43Z</dc:date>
    <item>
      <title>Lakeflow jobs file trigger thru overwritten files</title>
      <link>https://community.databricks.com/t5/get-started-discussions/lakeflow-jobs-file-trigger-thru-overwritten-files/m-p/155567#M11721</link>
      <description>&lt;P&gt;Is there any way a job can be triggered with overwritten files through a file trigger?&lt;/P&gt;&lt;P&gt;I knew the limitations, but I just want to have other opinions or solutions.&lt;/P&gt;&lt;H2 id="-limitations"&gt;&lt;FONT color="#FF6600"&gt;Limitations&lt;/FONT&gt;&lt;/H2&gt;&lt;UL&gt;&lt;LI&gt;&lt;FONT color="#FF6600"&gt;Only new files trigger runs. Overwriting an existing file with a file of the same name does not trigger a run.&lt;/FONT&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Thank you in advance!&lt;/P&gt;</description>
      <pubDate>Mon, 27 Apr 2026 12:33:47 GMT</pubDate>
      <guid>https://community.databricks.com/t5/get-started-discussions/lakeflow-jobs-file-trigger-thru-overwritten-files/m-p/155567#M11721</guid>
      <dc:creator>DazzaiDe</dc:creator>
      <dc:date>2026-04-27T12:33:47Z</dc:date>
    </item>
    <item>
      <title>Re: Lakeflow jobs file trigger thru overwritten files</title>
      <link>https://community.databricks.com/t5/get-started-discussions/lakeflow-jobs-file-trigger-thru-overwritten-files/m-p/155572#M11722</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/227755"&gt;@DazzaiDe&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Unfortunately, you can't do that as of today.&lt;/P&gt;
&lt;P&gt;Is there a specific reason you want to maintain the same name for the triggers? Instead of linking to a static file name, could you point to a root path so that any new files will trigger the job? If this approach is acceptable, you might consider appending a value, like a timestamp, to the files each day, which would allow them to be recognised as new files?&lt;/P&gt;
&lt;P&gt;The other option is to schedule it to run every few minutes or hours. This approach should work, but it’s not event-driven, to be honest.&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;I&gt;&lt;/I&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 27 Apr 2026 13:48:14 GMT</pubDate>
      <guid>https://community.databricks.com/t5/get-started-discussions/lakeflow-jobs-file-trigger-thru-overwritten-files/m-p/155572#M11722</guid>
      <dc:creator>Ashwin_DSA</dc:creator>
      <dc:date>2026-04-27T13:48:14Z</dc:date>
    </item>
    <item>
      <title>Re: Lakeflow jobs file trigger thru overwritten files</title>
      <link>https://community.databricks.com/t5/get-started-discussions/lakeflow-jobs-file-trigger-thru-overwritten-files/m-p/155640#M11723</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/216690"&gt;@Ashwin_DSA&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;Btw, my trigger is pointed to a root path already. My goal is to reprocess any file (if they reupload the raw file again because of some fixes to the data). It's possible with autoloader (reprocess overwritten files), but my problem is how I will automatically trigger the job.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Apr 2026 06:57:43 GMT</pubDate>
      <guid>https://community.databricks.com/t5/get-started-discussions/lakeflow-jobs-file-trigger-thru-overwritten-files/m-p/155640#M11723</guid>
      <dc:creator>DazzaiDe</dc:creator>
      <dc:date>2026-04-28T06:57:43Z</dc:date>
    </item>
    <item>
      <title>Re: Lakeflow jobs file trigger thru overwritten files</title>
      <link>https://community.databricks.com/t5/get-started-discussions/lakeflow-jobs-file-trigger-thru-overwritten-files/m-p/155729#M11726</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/227755"&gt;@DazzaiDe&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Understood. Does &lt;A href="https://community.databricks.com/t5/technical-blog/partner-blog-beyond-adls-limits-file-arrival-triggers-for-file/ba-p/141760" target="_blank"&gt;this&lt;/A&gt; help?&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;I&gt;&lt;/I&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Apr 2026 17:51:18 GMT</pubDate>
      <guid>https://community.databricks.com/t5/get-started-discussions/lakeflow-jobs-file-trigger-thru-overwritten-files/m-p/155729#M11726</guid>
      <dc:creator>Ashwin_DSA</dc:creator>
      <dc:date>2026-04-28T17:51:18Z</dc:date>
    </item>
  </channel>
</rss>

