<?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 QlikView 12 kills scheduled tasks after waiting for 45 minutes for an engine in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/QlikView-12-kills-scheduled-tasks-after-waiting-for-45-minutes/m-p/65481#M1248984</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We recently upgraded to QlikView 12.&amp;nbsp; I noticed today that a key scheduled task had not started for some reason.&amp;nbsp; After digging through the Publisher log file (Root_2018xxxx.txt), I found the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;20180507T064501.532-0500 Information TriggerState: Change State to Ignored. Task="My Task Name", ExecId=6773395f-57f9-445f-94a8-bd450028f311. Trigger ScheduleTrigger ignored. No QlikView Engine was available after waiting for 45 minutes.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is really unacceptable to not start a task like this and without any error notification of any kind.&amp;nbsp; It can have many consequences, often resulting in stale data.&amp;nbsp; In my case, an entire sequence of Production tasks was left quietly unexecuted!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question:&amp;nbsp; Is there a way to disable this bug or at least change the 45 minutes to a much larger time period?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 26 Jan 2026 18:19:17 GMT</pubDate>
    <dc:creator>kevinpintokpa</dc:creator>
    <dc:date>2026-01-26T18:19:17Z</dc:date>
    <item>
      <title>QlikView 12 kills scheduled tasks after waiting for 45 minutes for an engine</title>
      <link>https://community.qlik.com/t5/QlikView/QlikView-12-kills-scheduled-tasks-after-waiting-for-45-minutes/m-p/65481#M1248984</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We recently upgraded to QlikView 12.&amp;nbsp; I noticed today that a key scheduled task had not started for some reason.&amp;nbsp; After digging through the Publisher log file (Root_2018xxxx.txt), I found the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;20180507T064501.532-0500 Information TriggerState: Change State to Ignored. Task="My Task Name", ExecId=6773395f-57f9-445f-94a8-bd450028f311. Trigger ScheduleTrigger ignored. No QlikView Engine was available after waiting for 45 minutes.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is really unacceptable to not start a task like this and without any error notification of any kind.&amp;nbsp; It can have many consequences, often resulting in stale data.&amp;nbsp; In my case, an entire sequence of Production tasks was left quietly unexecuted!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question:&amp;nbsp; Is there a way to disable this bug or at least change the 45 minutes to a much larger time period?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jan 2026 18:19:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/QlikView-12-kills-scheduled-tasks-after-waiting-for-45-minutes/m-p/65481#M1248984</guid>
      <dc:creator>kevinpintokpa</dc:creator>
      <dc:date>2026-01-26T18:19:17Z</dc:date>
    </item>
    <item>
      <title>Re: QlikView 12 kills scheduled tasks after waiting for 45 minutes for an engine</title>
      <link>https://community.qlik.com/t5/QlikView/QlikView-12-kills-scheduled-tasks-after-waiting-for-45-minutes/m-p/65482#M1248987</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is not a bug and this behavior was exactly the same in 11.20. After 45 minutes waiting for a free reload engine, the QDS will simply give up.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are a few solutions for your situation:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;either configure more reload engines. See QMC-&amp;gt;System-&amp;gt;Setup-&amp;gt;Distribution Services-&amp;gt;Your QDS-&amp;gt;Advanced-&amp;gt;QlikView Engine. You should not configure more reload engines than there are cores in your server CPU(s).&lt;/LI&gt;&lt;LI&gt;or (and this probably existed in the old environment, but you may have forgotten to take it along when upgrading to v12), increase the wait period for a reload engine to become available. See &lt;A href="https://community.qlik.com/message/875573"&gt;Re: Server-Task delaying&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Peter&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 May 2018 08:27:55 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/QlikView-12-kills-scheduled-tasks-after-waiting-for-45-minutes/m-p/65482#M1248987</guid>
      <dc:creator>Peter_Cammaert</dc:creator>
      <dc:date>2018-05-08T08:27:55Z</dc:date>
    </item>
    <item>
      <title>Re: QlikView 12 kills scheduled tasks after waiting for 45 minutes for an engine</title>
      <link>https://community.qlik.com/t5/QlikView/QlikView-12-kills-scheduled-tasks-after-waiting-for-45-minutes/m-p/65483#M1248989</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, I followed your second option of increasing the QvbWaitTimeoutMinutes from 45 to 90 minutes.&amp;nbsp; That seemed to be enough for my environment.&amp;nbsp; No silent failures today!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 May 2018 22:23:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/QlikView-12-kills-scheduled-tasks-after-waiting-for-45-minutes/m-p/65483#M1248989</guid>
      <dc:creator>kevinpintokpa</dc:creator>
      <dc:date>2018-05-09T22:23:22Z</dc:date>
    </item>
  </channel>
</rss>

