<?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: Qlik Compose task restart leads to repeated execution of completed steps in Qlik Compose</title>
    <link>https://community.qlik.com/t5/Qlik-Compose/Qlik-Compose-task-restart-leads-to-repeated-execution-of/m-p/2537566#M2042</link>
    <description>&lt;P&gt;If I had to choose just one data integration tool for a project requiring continuous data movement across both on-premises and cloud environments, I would choose Qlik Data Integration (QDI).&lt;/P&gt;&lt;P&gt;&lt;!--  StartFragment   --&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN class=""&gt;&lt;STRONG&gt;On-Premises Sources:&lt;/STRONG&gt; Good support for legacy databases (like SAP, DB2 etc) and&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;relational databases (like Oracle, SQL Server, PostgreSQL etc).&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN class=""&gt;&lt;STRONG&gt;Cloud Targets:&lt;/STRONG&gt; Natively supports and optimizes data loading into major cloud data warehouses and lakes (e.g., Snowflake, Amazon Redshift, &lt;/SPAN&gt;&lt;SPAN class=""&gt;and Azure)&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
    <pubDate>Sat, 29 Nov 2025 06:57:54 GMT</pubDate>
    <dc:creator>Nagaraju_KCS</dc:creator>
    <dc:date>2025-11-29T06:57:54Z</dc:date>
    <item>
      <title>Qlik Compose task restart leads to repeated execution of completed steps</title>
      <link>https://community.qlik.com/t5/Qlik-Compose/Qlik-Compose-task-restart-leads-to-repeated-execution-of/m-p/2536712#M2040</link>
      <description>&lt;P&gt;We have a workflow consisting of multiple ETL tasks. Each task processes several interrelated entities. Currently, Compose does not provide a checkpoint feature, so if a task fails, rerunning the job starts from the beginning instead of resuming from the point of failure. This leads to repeated execution of completed steps, resulting in longer runtimes and increased resource consumption. Could you suggest a solution for this? Splitting into one task per entity is not an option for us.&lt;/P&gt;</description>
      <pubDate>Thu, 20 Nov 2025 07:15:50 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Compose/Qlik-Compose-task-restart-leads-to-repeated-execution-of/m-p/2536712#M2040</guid>
      <dc:creator>Reshmaf</dc:creator>
      <dc:date>2025-11-20T07:15:50Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Compose task restart leads to repeated execution of completed steps</title>
      <link>https://community.qlik.com/t5/Qlik-Compose/Qlik-Compose-task-restart-leads-to-repeated-execution-of/m-p/2537566#M2042</link>
      <description>&lt;P&gt;If I had to choose just one data integration tool for a project requiring continuous data movement across both on-premises and cloud environments, I would choose Qlik Data Integration (QDI).&lt;/P&gt;&lt;P&gt;&lt;!--  StartFragment   --&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN class=""&gt;&lt;STRONG&gt;On-Premises Sources:&lt;/STRONG&gt; Good support for legacy databases (like SAP, DB2 etc) and&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;relational databases (like Oracle, SQL Server, PostgreSQL etc).&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN class=""&gt;&lt;STRONG&gt;Cloud Targets:&lt;/STRONG&gt; Natively supports and optimizes data loading into major cloud data warehouses and lakes (e.g., Snowflake, Amazon Redshift, &lt;/SPAN&gt;&lt;SPAN class=""&gt;and Azure)&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Sat, 29 Nov 2025 06:57:54 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Compose/Qlik-Compose-task-restart-leads-to-repeated-execution-of/m-p/2537566#M2042</guid>
      <dc:creator>Nagaraju_KCS</dc:creator>
      <dc:date>2025-11-29T06:57:54Z</dc:date>
    </item>
  </channel>
</rss>

