<?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: scheduling in dlt pipeline in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/scheduling-in-dlt-pipeline/m-p/144630#M52355</link>
    <description>&lt;P&gt;This seems like a know limitation at the moment . Similar post from prior discussion and workaround as follows&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.databricks.com/t5/data-engineering/databricks-asset-bundles-triggering-delta-live-tables/td-p/108795" target="_blank"&gt;https://community.databricks.com/t5/data-engineering/databricks-asset-bundles-triggering-delta-live-tables/td-p/108795&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 20 Jan 2026 17:38:41 GMT</pubDate>
    <dc:creator>pradeep_singh</dc:creator>
    <dc:date>2026-01-20T17:38:41Z</dc:date>
    <item>
      <title>scheduling in dlt pipeline</title>
      <link>https://community.databricks.com/t5/data-engineering/scheduling-in-dlt-pipeline/m-p/144624#M52354</link>
      <description>&lt;P&gt;Hi Team,&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;when i creaing DLT pipelines i am not able add&amp;nbsp;scheduls via assed bundle,&lt;/P&gt;&lt;P&gt;its allowing me from UI only&lt;BR /&gt;is there any other option make dynamic way to create schdules like using SDK | API | CLI&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jan 2026 17:03:49 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/scheduling-in-dlt-pipeline/m-p/144624#M52354</guid>
      <dc:creator>rvakr</dc:creator>
      <dc:date>2026-01-20T17:03:49Z</dc:date>
    </item>
    <item>
      <title>Re: scheduling in dlt pipeline</title>
      <link>https://community.databricks.com/t5/data-engineering/scheduling-in-dlt-pipeline/m-p/144630#M52355</link>
      <description>&lt;P&gt;This seems like a know limitation at the moment . Similar post from prior discussion and workaround as follows&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.databricks.com/t5/data-engineering/databricks-asset-bundles-triggering-delta-live-tables/td-p/108795" target="_blank"&gt;https://community.databricks.com/t5/data-engineering/databricks-asset-bundles-triggering-delta-live-tables/td-p/108795&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jan 2026 17:38:41 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/scheduling-in-dlt-pipeline/m-p/144630#M52355</guid>
      <dc:creator>pradeep_singh</dc:creator>
      <dc:date>2026-01-20T17:38:41Z</dc:date>
    </item>
    <item>
      <title>Re: scheduling in dlt pipeline</title>
      <link>https://community.databricks.com/t5/data-engineering/scheduling-in-dlt-pipeline/m-p/144633#M52357</link>
      <description>&lt;P&gt;Unfortunately, you can't set it in YAML directly.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;A workaround for this would be to create the pipeline as a triggered pipeline, and then create a job that will trigger the pipeline periodically. Unlike pipelines, job schedules&amp;nbsp;&lt;EM&gt;can&lt;/EM&gt; be defined using the YAML.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Something like the following would probably get the job done:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;# resources/my_pipeline_job.yml
resources:
  jobs:
    scheduled_dlt_pipeline:
      name: "Scheduled DLT Pipeline Job"
      schedule:
        quartz_cron_expression: "0 0 8 * * ?"  # Daily at 8 AM
        timezone_id: "America/Chicago"
        pause_status: "UNPAUSED"
      tasks:
        - task_key: run_dlt_pipeline
          pipeline_task:
            pipeline_id: ${resources.pipelines.my_dlt_pipeline.id}
      email_notifications:
        on_failure:
          - data-team@company.com
&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jan 2026 17:45:43 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/scheduling-in-dlt-pipeline/m-p/144633#M52357</guid>
      <dc:creator>davidmorton</dc:creator>
      <dc:date>2026-01-20T17:45:43Z</dc:date>
    </item>
    <item>
      <title>Re: scheduling in dlt pipeline</title>
      <link>https://community.databricks.com/t5/data-engineering/scheduling-in-dlt-pipeline/m-p/144634#M52358</link>
      <description>&lt;P&gt;Using workflows to trigger DLT pipelines give you couple of other flexibilities as well so I would recommend that approach.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jan 2026 17:49:22 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/scheduling-in-dlt-pipeline/m-p/144634#M52358</guid>
      <dc:creator>pradeep_singh</dc:creator>
      <dc:date>2026-01-20T17:49:22Z</dc:date>
    </item>
    <item>
      <title>Re: scheduling in dlt pipeline</title>
      <link>https://community.databricks.com/t5/data-engineering/scheduling-in-dlt-pipeline/m-p/144637#M52360</link>
      <description>&lt;P&gt;If you still want to use sdk here is what you can do . update the job using sdk&lt;/P&gt;&lt;LI-CODE lang="python"&gt;from databricks.sdk import WorkspaceClient

w = WorkspaceClient()

def update_job_schedule(job_id: int):
    return w.jobs.update(
        job_id=job_id,
        new_settings={
            "schedule": {
                "quartz_cron_expression": "0 0 1 * * ?",
                "timezone_id": "UTC",
                "pause_status": "UNPAUSED",
            }
        },
    )

result = update_job_schedule(1234567890)
print(result)&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jan 2026 17:55:33 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/scheduling-in-dlt-pipeline/m-p/144637#M52360</guid>
      <dc:creator>pradeep_singh</dc:creator>
      <dc:date>2026-01-20T17:55:33Z</dc:date>
    </item>
    <item>
      <title>Re: scheduling in dlt pipeline</title>
      <link>https://community.databricks.com/t5/data-engineering/scheduling-in-dlt-pipeline/m-p/144650#M52364</link>
      <description>&lt;P&gt;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/202980"&gt;@pradeep_singh&lt;/a&gt;&amp;nbsp; Thanks for update&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jan 2026 18:53:14 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/scheduling-in-dlt-pipeline/m-p/144650#M52364</guid>
      <dc:creator>rvakr</dc:creator>
      <dc:date>2026-01-20T18:53:14Z</dc:date>
    </item>
  </channel>
</rss>

