<?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 Task Restart After EC2 Restart or Crash in Qlik Replicate</title>
    <link>https://community.qlik.com/t5/Qlik-Replicate/Task-Restart-After-EC2-Restart-or-Crash/m-p/2553430#M16548</link>
    <description>&lt;P&gt;I have a task that perform a full load once a month. In the past, I have experienced multiple instances where the EC2 instance hosting replicate task was restarted in the middle of the task execution as part of the scheduled monthly maintenance.&lt;/P&gt;&lt;P&gt;When this happens, once the EC2 instance comes back online, the replicate task automatically restart from the beginning. As a result, duplicate records are inserted into the target tables for the data that had already been loaded before the interruption.&lt;/P&gt;&lt;P&gt;To prevent this, I configured&amp;nbsp;abnormal_count": 0 under recoverable_error_behavior and tested the scenario by simulating and unexpected restart. However, even with&amp;nbsp;abnormal_count set to 0, the task still restart automatically after the EC2 instance is back online.&lt;/P&gt;&lt;P&gt;Is there a way to prevent the task from automatically restarting after the EC2 reboot, or is there a recommended approach to handle this scenario and avoid duplicate data? Any suggestion would be greatly appreciated.&lt;/P&gt;</description>
    <pubDate>Fri, 17 Jul 2026 18:50:57 GMT</pubDate>
    <dc:creator>NewbieQlik</dc:creator>
    <dc:date>2026-07-17T18:50:57Z</dc:date>
    <item>
      <title>Task Restart After EC2 Restart or Crash</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Task-Restart-After-EC2-Restart-or-Crash/m-p/2553430#M16548</link>
      <description>&lt;P&gt;I have a task that perform a full load once a month. In the past, I have experienced multiple instances where the EC2 instance hosting replicate task was restarted in the middle of the task execution as part of the scheduled monthly maintenance.&lt;/P&gt;&lt;P&gt;When this happens, once the EC2 instance comes back online, the replicate task automatically restart from the beginning. As a result, duplicate records are inserted into the target tables for the data that had already been loaded before the interruption.&lt;/P&gt;&lt;P&gt;To prevent this, I configured&amp;nbsp;abnormal_count": 0 under recoverable_error_behavior and tested the scenario by simulating and unexpected restart. However, even with&amp;nbsp;abnormal_count set to 0, the task still restart automatically after the EC2 instance is back online.&lt;/P&gt;&lt;P&gt;Is there a way to prevent the task from automatically restarting after the EC2 reboot, or is there a recommended approach to handle this scenario and avoid duplicate data? Any suggestion would be greatly appreciated.&lt;/P&gt;</description>
      <pubDate>Fri, 17 Jul 2026 18:50:57 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Task-Restart-After-EC2-Restart-or-Crash/m-p/2553430#M16548</guid>
      <dc:creator>NewbieQlik</dc:creator>
      <dc:date>2026-07-17T18:50:57Z</dc:date>
    </item>
    <item>
      <title>Re: Task Restart After EC2 Restart or Crash</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Task-Restart-After-EC2-Restart-or-Crash/m-p/2553441#M16549</link>
      <description>&lt;P&gt;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/128304"&gt;@NewbieQlik&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;SPAN&gt;As per issue description.&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;UL data-spread="false"&gt;
&lt;LI&gt;&lt;SPAN&gt;Restarting the EC2 instance during task execution causes Replicate to start the task in &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Fresh Start&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt; mode.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;&lt;SPAN&gt;Full Load + CDC&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt; tasks restart the full load instead of resuming from the last checkpoint.This happened because it error occurred as there is a error status code mentioned below&amp;nbsp; it&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;the&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE dir="ltr"&gt;&lt;STRONG&gt;&lt;SPAN&gt;recoverable_error_behavior.abnormal_count=0&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/CODE&gt;&lt;SPAN&gt; setting does &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;not&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt; apply because a service restart is &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;not&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt; treated as a recoverable error.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Recoverable error settings only handle runtime errors (for example, connection interruptions), not Replicate service or host restarts.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN&gt;You may choose below steps to avoid Future occurrence&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL data-spread="false"&gt;
&lt;LI&gt;&lt;SPAN&gt;Manually &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Stop&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt; all running Replicate tasks.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;This ensures the current task state is saved correctly.&lt;/SPAN&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;SPAN&gt;do the maintenance&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Start the Replicate service.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;&lt;SPAN&gt;Resume&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt; the tasks to continue from the last saved checkpoint, or perform a &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Reload&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt; only if required.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN&gt;Sushil Kumar&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 19 Jul 2026 08:12:28 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Task-Restart-After-EC2-Restart-or-Crash/m-p/2553441#M16549</guid>
      <dc:creator>SushilKumar</dc:creator>
      <dc:date>2026-07-19T08:12:28Z</dc:date>
    </item>
    <item>
      <title>Re: Task Restart After EC2 Restart or Crash</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Task-Restart-After-EC2-Restart-or-Crash/m-p/2553467#M16550</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/128304"&gt;@NewbieQlik&lt;/a&gt;&amp;nbsp;,&lt;BR /&gt;&lt;BR /&gt;How is the &lt;STRONG data-index-in-node="11" data-path-to-node="7,0"&gt;"If target table already exists"&lt;/STRONG&gt; option currently set in the Full Load settings? Please try "&lt;SPAN class="non-edit-text ng-binding" title="TRUNCATE before loading"&gt;TRUNCATE before loading" to see if that helps.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Desmond&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Desmond&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Jul 2026 08:20:55 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Task-Restart-After-EC2-Restart-or-Crash/m-p/2553467#M16550</guid>
      <dc:creator>DesmondWOO</dc:creator>
      <dc:date>2026-07-20T08:20:55Z</dc:date>
    </item>
  </channel>
</rss>

