<?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: DLT Issue in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/dlt-issue/m-p/160235#M54870</link>
    <description>&lt;P&gt;A few details would help narrow this down.&lt;/P&gt;&lt;P&gt;When the scheduled run executes:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;Does the pipeline update show &lt;STRONG&gt;Succeeded&lt;/STRONG&gt; or &lt;STRONG&gt;Failed&lt;/STRONG&gt;?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;In the pipeline &lt;STRONG&gt;Event Log&lt;/STRONG&gt;, do you see rows being processed/written?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Is your manual run a normal update or a &lt;STRONG&gt;Full Refresh&lt;/STRONG&gt;?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Is the schedule configured directly on the DLT pipeline or triggered through a Workflow/Job?&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Common causes are:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;No new data available at the scheduled time&lt;/STRONG&gt; (the update succeeds but processes 0 rows).&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Incremental processing vs Full Refresh&lt;/STRONG&gt; (manual full refresh reprocesses historical data, scheduled updates only process new data).&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Different configuration/parameters&lt;/STRONG&gt; between scheduled and manual runs.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Permission differences&lt;/STRONG&gt; if the pipeline is being triggered through another service or workflow.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;The first thing I'd check is the Event Log for a scheduled run and compare it to a successful manual run. If both succeed but the scheduled run shows 0 records processed, the issue is usually related to source data availability or incremental processing rather than the pipeline logic itself.&lt;/P&gt;</description>
    <pubDate>Tue, 23 Jun 2026 11:04:39 GMT</pubDate>
    <dc:creator>Yogasathyandrun</dc:creator>
    <dc:date>2026-06-23T11:04:39Z</dc:date>
    <item>
      <title>DLT Issue</title>
      <link>https://community.databricks.com/t5/data-engineering/dlt-issue/m-p/160192#M54866</link>
      <description>&lt;P&gt;&lt;SPAN&gt;I have one DLT pipeline in Databricks. When I schedule the pipeline, the data is not showing. However, when I run the pipeline manually, the data is displayed properly&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jun 2026 06:47:57 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/dlt-issue/m-p/160192#M54866</guid>
      <dc:creator>Databrickissue</dc:creator>
      <dc:date>2026-06-23T06:47:57Z</dc:date>
    </item>
    <item>
      <title>Re: DLT Issue</title>
      <link>https://community.databricks.com/t5/data-engineering/dlt-issue/m-p/160235#M54870</link>
      <description>&lt;P&gt;A few details would help narrow this down.&lt;/P&gt;&lt;P&gt;When the scheduled run executes:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;Does the pipeline update show &lt;STRONG&gt;Succeeded&lt;/STRONG&gt; or &lt;STRONG&gt;Failed&lt;/STRONG&gt;?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;In the pipeline &lt;STRONG&gt;Event Log&lt;/STRONG&gt;, do you see rows being processed/written?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Is your manual run a normal update or a &lt;STRONG&gt;Full Refresh&lt;/STRONG&gt;?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Is the schedule configured directly on the DLT pipeline or triggered through a Workflow/Job?&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Common causes are:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;No new data available at the scheduled time&lt;/STRONG&gt; (the update succeeds but processes 0 rows).&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Incremental processing vs Full Refresh&lt;/STRONG&gt; (manual full refresh reprocesses historical data, scheduled updates only process new data).&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Different configuration/parameters&lt;/STRONG&gt; between scheduled and manual runs.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Permission differences&lt;/STRONG&gt; if the pipeline is being triggered through another service or workflow.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;The first thing I'd check is the Event Log for a scheduled run and compare it to a successful manual run. If both succeed but the scheduled run shows 0 records processed, the issue is usually related to source data availability or incremental processing rather than the pipeline logic itself.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jun 2026 11:04:39 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/dlt-issue/m-p/160235#M54870</guid>
      <dc:creator>Yogasathyandrun</dc:creator>
      <dc:date>2026-06-23T11:04:39Z</dc:date>
    </item>
  </channel>
</rss>

