<?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 Query Tag - Session Timeout in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Query-Tag-Session-Timeout/m-p/2550025#M110341</link>
    <description>&lt;P&gt;Hello, we usually use a query tag to set context for our queries to our warehouse. It looks as follows:&lt;/P&gt;&lt;P&gt;LIB CONNECT TO 'Admin:Snowflake'; Let vAppName = DocumentTitle(); SQL alter session set query_tag='$(vAppName)' !EXECUTE_NON_SELECT_QUERY;&lt;/P&gt;&lt;P&gt;In the past we set this once at the beginning of the script. In Qlik Cloud, though, this doesn't seem to persist for the whole duration of the reload, so the information gets lost for some SQL loads later in the script. Is there a possibility to set this via the Snowflake connection as an advanced parameter, to get rid of this code snippet entirely?&lt;/P&gt;</description>
    <pubDate>Wed, 27 May 2026 14:24:24 GMT</pubDate>
    <dc:creator>Necator</dc:creator>
    <dc:date>2026-05-27T14:24:24Z</dc:date>
    <item>
      <title>Query Tag - Session Timeout</title>
      <link>https://community.qlik.com/t5/App-Development/Query-Tag-Session-Timeout/m-p/2550025#M110341</link>
      <description>&lt;P&gt;Hello, we usually use a query tag to set context for our queries to our warehouse. It looks as follows:&lt;/P&gt;&lt;P&gt;LIB CONNECT TO 'Admin:Snowflake'; Let vAppName = DocumentTitle(); SQL alter session set query_tag='$(vAppName)' !EXECUTE_NON_SELECT_QUERY;&lt;/P&gt;&lt;P&gt;In the past we set this once at the beginning of the script. In Qlik Cloud, though, this doesn't seem to persist for the whole duration of the reload, so the information gets lost for some SQL loads later in the script. Is there a possibility to set this via the Snowflake connection as an advanced parameter, to get rid of this code snippet entirely?&lt;/P&gt;</description>
      <pubDate>Wed, 27 May 2026 14:24:24 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Query-Tag-Session-Timeout/m-p/2550025#M110341</guid>
      <dc:creator>Necator</dc:creator>
      <dc:date>2026-05-27T14:24:24Z</dc:date>
    </item>
    <item>
      <title>Re: Query Tag - Session Timeout</title>
      <link>https://community.qlik.com/t5/App-Development/Query-Tag-Session-Timeout/m-p/2550304#M110359</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;Yes, if you're using Snowflake, the best practice is to set QUERY_TAG in the connection/session configuration rather than relying on ALTER SESSION once at the start of the script.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Check the Snowflake connection's Advanced Properties first. If QUERY_TAG isn't supported there, assume Qlik Cloud may create new sessions during reloads and set the tag again where needed.&lt;/P&gt;</description>
      <pubDate>Sat, 30 May 2026 17:38:27 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Query-Tag-Session-Timeout/m-p/2550304#M110359</guid>
      <dc:creator>Chanty4u</dc:creator>
      <dc:date>2026-05-30T17:38:27Z</dc:date>
    </item>
  </channel>
</rss>

