<?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: Holding Qlik App Reload in Script Level in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/Holding-Qlik-App-Reload-in-Script-Level/m-p/2161033#M26397</link>
    <description>&lt;P&gt;Sleep supports max. 1 hour. If you need more you will need a loop like:&lt;/P&gt;
&lt;DIV&gt;if num(weekday(today())) = 6 then&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp;for i = 1 to 6&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; sleep 1 * 60 * 59 * 1000 ;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp;next&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;else&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp;sleep 30;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;end if&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Depending on the entire run-time any timeouts might be touched. Default should be 5 hours before the task is terminated.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;A side-effect of the sleep-statements is an increase of the RAM consumption of the distribution-engine - not the task-running qvb.exe - because there is more internal communication + logging. But in a properly sized environment it won't be critically.&lt;/DIV&gt;</description>
    <pubDate>Fri, 12 Jan 2024 11:07:49 GMT</pubDate>
    <dc:creator>marcus_sommer</dc:creator>
    <dc:date>2024-01-12T11:07:49Z</dc:date>
    <item>
      <title>Holding Qlik App Reload in Script Level</title>
      <link>https://community.qlik.com/t5/Management-Governance/Holding-Qlik-App-Reload-in-Script-Level/m-p/2160994#M26394</link>
      <description>&lt;P&gt;Hi Team ⁠&lt;span class="lia-unicode-emoji" title=":woman_technologist:"&gt;👩‍💻&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Need a help : &lt;BR /&gt;was trying to write a logic in Qlik script level which will hold the Qlik app reload untill today's data is available to display in the dashboard.&lt;BR /&gt;Any clue on this?&lt;/P&gt;
&lt;P&gt;Sleep will be good I guess but not sure about the qlik engine utilization for the same in case the qlik app reload process is sleeping for a long time (e.g: 2 hours etc.)&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;As usual, advance thanks for your help ⁠.&lt;BR /&gt;Cheers!!&amp;nbsp;&lt;BR /&gt;Happy Weekend.&lt;BR /&gt;-Chalorme&lt;span class="lia-unicode-emoji" title=":smiling_face_with_smiling_eyes:"&gt;😊&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 12 Jan 2024 09:52:15 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Holding-Qlik-App-Reload-in-Script-Level/m-p/2160994#M26394</guid>
      <dc:creator>Chalorme</dc:creator>
      <dc:date>2024-01-12T09:52:15Z</dc:date>
    </item>
    <item>
      <title>Re: Holding Qlik App Reload in Script Level</title>
      <link>https://community.qlik.com/t5/Management-Governance/Holding-Qlik-App-Reload-in-Script-Level/m-p/2161033#M26397</link>
      <description>&lt;P&gt;Sleep supports max. 1 hour. If you need more you will need a loop like:&lt;/P&gt;
&lt;DIV&gt;if num(weekday(today())) = 6 then&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp;for i = 1 to 6&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; sleep 1 * 60 * 59 * 1000 ;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp;next&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;else&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp;sleep 30;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;end if&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Depending on the entire run-time any timeouts might be touched. Default should be 5 hours before the task is terminated.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;A side-effect of the sleep-statements is an increase of the RAM consumption of the distribution-engine - not the task-running qvb.exe - because there is more internal communication + logging. But in a properly sized environment it won't be critically.&lt;/DIV&gt;</description>
      <pubDate>Fri, 12 Jan 2024 11:07:49 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Holding-Qlik-App-Reload-in-Script-Level/m-p/2161033#M26397</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2024-01-12T11:07:49Z</dc:date>
    </item>
    <item>
      <title>Re: Holding Qlik App Reload in Script Level</title>
      <link>https://community.qlik.com/t5/Management-Governance/Holding-Qlik-App-Reload-in-Script-Level/m-p/2163293#M26440</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/77083"&gt;@Chalorme&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Generally I do not recommend sleep due to resource consumption issues, in addition to taking up a place in the number of simultaneous recharges that can be performed.&lt;/P&gt;
&lt;P&gt;If you still want to go that route, what &lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/28038"&gt;@marcus_sommer&lt;/a&gt;&amp;nbsp;says will work for you.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Instead of doing that, I would prefer to implement a small task that checks from time to time if the condition is already met, and if so, a chained task is triggered.&lt;/P&gt;
&lt;P&gt;Also, I like it better that the external process that is consolidating data uses the Qlik Sense API to trigger a task&lt;/P&gt;
&lt;P&gt;&lt;A href="https://github.com/marcusspitzmiller/QlikSenseTask" target="_blank"&gt;https://github.com/marcusspitzmiller/QlikSenseTask&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps.&lt;/P&gt;
&lt;P&gt;best&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;help users find answers! Don't forget to&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;FONT color="#993366"&gt;mark a solution&lt;/FONT&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;that worked for you &amp;amp; to smash the&lt;FONT color="#339966"&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;like&lt;/FONT&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;button!&amp;nbsp;&lt;/STRONG&gt;&lt;span class="lia-unicode-emoji" title=":smiling_face_with_smiling_eyes:"&gt;😊&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jan 2024 13:12:57 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Holding-Qlik-App-Reload-in-Script-Level/m-p/2163293#M26440</guid>
      <dc:creator>RafaelBarrios</dc:creator>
      <dc:date>2024-01-19T13:12:57Z</dc:date>
    </item>
    <item>
      <title>Re: Holding Qlik App Reload in Script Level</title>
      <link>https://community.qlik.com/t5/Management-Governance/Holding-Qlik-App-Reload-in-Script-Level/m-p/2163337#M26443</link>
      <description>&lt;P&gt;If there is a publisher in place multiple triggers per application could be set which might be used to branch into various task-chains. But without a publisher a single trigger must fulfill all requirements which limits the possibilities quite significantly ...&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jan 2024 14:56:21 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Holding-Qlik-App-Reload-in-Script-Level/m-p/2163337#M26443</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2024-01-19T14:56:21Z</dc:date>
    </item>
    <item>
      <title>Re: Holding Qlik App Reload in Script Level</title>
      <link>https://community.qlik.com/t5/Management-Governance/Holding-Qlik-App-Reload-in-Script-Level/m-p/2163491#M26446</link>
      <description>&lt;P&gt;True &lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/28038"&gt;@marcus_sommer&lt;/a&gt;&amp;nbsp;, but considering we are talking about Qlik sense client managed, you could make that task to fail if the condition it’s not fulfilled, and let it finish if it’s ok so it triggers the following task&lt;/P&gt;
&lt;P&gt;this is an example, one task depending on a dummy task that will only execute if dummy execute successfully&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="RafaelBarrios_0-1705703735037.jpeg" style="width: 1284px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/127461i9B5DBDF0FBE570F7/image-size/medium?v=v2&amp;amp;px=400" role="button" title="RafaelBarrios_0-1705703735037.jpeg" alt="RafaelBarrios_0-1705703735037.jpeg" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;I still like more the API Way, so you have another program that calls the Qlik Sense task once it’s ready.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps.&lt;/P&gt;
&lt;P&gt;Best,&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;help users find answers! Don't forget to&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;FONT color="#993366"&gt;mark a solution&lt;/FONT&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;that worked for you &amp;amp; to smash the&lt;FONT color="#339966"&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;like&lt;/FONT&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;button!&amp;nbsp;&lt;/STRONG&gt;&lt;SPAN class="lia-unicode-emoji" title=":smiling_face_with_smiling_eyes:"&gt;&lt;span class="lia-unicode-emoji" title=":smiling_face_with_smiling_eyes:"&gt;😊&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jan 2024 22:39:00 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Holding-Qlik-App-Reload-in-Script-Level/m-p/2163491#M26446</guid>
      <dc:creator>RafaelBarrios</dc:creator>
      <dc:date>2024-01-19T22:39:00Z</dc:date>
    </item>
  </channel>
</rss>

