<?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 DLT started by SERVICE_UPGRADE in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/dlt-started-by-service-upgrade/m-p/2856#M128</link>
    <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm developing a dlt pipeline, configured in continuous mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm still in dev mode, so I stop my pipeline when i'm not working on it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My problem is that the pipeline is frequently started by SERVICE_UPGRADE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;example of message:&lt;/P&gt;&lt;P&gt;'Update xxxxx started by SERVICE_UPGRADE'&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It generates costs, even more when this happens during the weekend...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone experienced the same behaviour? is there a way to prevent it ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Mon, 19 Jun 2023 08:47:19 GMT</pubDate>
    <dc:creator>alemo</dc:creator>
    <dc:date>2023-06-19T08:47:19Z</dc:date>
    <item>
      <title>DLT started by SERVICE_UPGRADE</title>
      <link>https://community.databricks.com/t5/data-engineering/dlt-started-by-service-upgrade/m-p/2856#M128</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm developing a dlt pipeline, configured in continuous mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm still in dev mode, so I stop my pipeline when i'm not working on it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My problem is that the pipeline is frequently started by SERVICE_UPGRADE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;example of message:&lt;/P&gt;&lt;P&gt;'Update xxxxx started by SERVICE_UPGRADE'&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It generates costs, even more when this happens during the weekend...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone experienced the same behaviour? is there a way to prevent it ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jun 2023 08:47:19 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/dlt-started-by-service-upgrade/m-p/2856#M128</guid>
      <dc:creator>alemo</dc:creator>
      <dc:date>2023-06-19T08:47:19Z</dc:date>
    </item>
    <item>
      <title>Re: DLT started by SERVICE_UPGRADE</title>
      <link>https://community.databricks.com/t5/data-engineering/dlt-started-by-service-upgrade/m-p/2857#M129</link>
      <description>&lt;P&gt;Hi @alex mo​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Great to meet you, and thanks for your question! &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let's see if your peers in the community have an answer to your question. Thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jun 2023 04:38:28 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/dlt-started-by-service-upgrade/m-p/2857#M129</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-06-20T04:38:28Z</dc:date>
    </item>
  </channel>
</rss>

