This document explains the differences between Talend License Levels, and describes important steps that must be completed before lowering your license level with Talend products. Talend offers three different license levels: listed from advanced to basic, they are Master Data Management, Data Management, and Data Integration/ESB. Talend projects, Jobs, and components are not compatible across each of the licenses available, so if you lower a license without first performing the proper steps, the potential for critical problems is high. This document will help you successfully lower your license level with Talend products.

This article is relating to downgrading Talend Data Fabric license to Talend Real-Time Big Data Platform. The difference between the licenses is that the MDM features/user type is removed for RTBDP licenses. If you have a Talend Data Fabric license with any MDM projects, you'll need to proceed with the following steps below.

Understanding the three licenses and how they are layered

Licenses

The license used in Talend Administration Center enables an administrator to create and administer projects and users of different types. You can see what licenses you have available in Talend Administration Center by navigating to the Menu tree > Settings > Licenses.

The table below describes what you can do in your product according to your user type and license

Preparation & Migration

The example used here will be downgrading from Master Data Management to Data Management. If you are downgrading from Master Data Management or Data Management to Data Integration/ESB, the concept will be the same

Projects

You must create new projects inside of Talend Administration Center with the project type of Data Management, or to the level of the license you are downgrading to. To complete this part, you must log into TAC and locate Projects under the Menu tree. Since you are not able to change the project type on an existing project, you may duplicate a project, then select the correct project type. If you are connecting to GIT, verify that the settings and URL are correct under the Advanced Settings after duplicating or creating a new project.


 

Authorization

After the new project with the correct license level is created, you will not be able to see the project available in Studio until you provide the users with permissions. Inside of TAC, you will need to locate Project Authorizations under the Menu tree. Here you must choose the new project and provide the users with the desired permissions on the right side. In the Rights column, you can choose to give either Read Only or Read/Write by choosing the icon with the person and pencil. If you have any groups, you will need to choose the tab at the top center Authorization by User/Group to make sure the groups also have the proper permissions.


 

Users

Log into Talend Administration Center, navigate to the Menu tree, and locate Users. You must lower the users from MDM to DM (or the desired license level) on the right-side panel of each user that is selected. If applicable, you should verify that their GIT user is correct.

During this process, you should keep one user at your current license level until the end of the downgrading project, preferably the admin user.

If you are unable to change the user type, you may not have the proper permissions or the user may still be logged in.

To verify if the user is logged in, check the Users page of Talend Administration Center. You can see which users are logged into the Talend Studio, Talend Data Preparation, and Talend Administration Center. Log them out if needed.

Data Preparation and Talend Data Stewardship will not be covered in depth, but if the user is a Data Preparation or TDS user be sure to check the Data Preparation User box and select their desired roles.

Migration

To begin this portion, log in as the user at your current license level, as discussed in the Users section.

When you start up your Studio, be sure to choose the existing projects that have your current license level. If you are doing remote, you can verify the user that you are logging in with, so you know you are entering the correct projects and have proper permissions.



Once you have logged in to your current project, you will need to begin exporting your Jobs into a specified location.

To export a Job:

1. Right-click the Job, and select Export Job.
2. To the right of Select archive file, click Browse to choose the destination and name for the Job ZIP archive.
3. Select the Job Version.
4. Check the box to Export Dependencies.
5. Check all Options.
6. Click Finish.

You will then want to log into the new project, which should be empty and have the license level you will be downgrading to. Once you have logged in to that project, you will need to import the jobs you previously exported.


To import a Job:

1. Right-click Job Designs in the Repository, then select the Import items option.
2. In the next window, browse to a root directory or an archive file path where your exported items are stored. A list of items appears in the table.
3. Select the items you want to import. Choose the Overwrite existing items option if the items already exist in your repository and you want to overwrite them.
4. Click Finish.
5. If the newly-imported items do not appear, click Refresh to refresh the Repository.

Components

Once you have imported your Jobs, you will want to test them in the new project and verify that the components work and are not a part of the higher-level license that you plan to downgrade from. To confirm that your components function properly, review the Component Reference Guide

If you have any schedules, it would be a best practice to verify the Jobs run on the schedulers and any other unique designs you may have implemented.

Once you have verified that your Jobs run successfully on the new license platform, request the downgraded license from your Customer Success Manager.

Environment

Talend Administration Center 

Talend Studio 

Capability

While there is a lot of hype around #AI in the world, there is no denying it's power ... for the RIGHT USE CASES.

Imagine the ability to ask Natural Language questions of the data you have in ServiceNow without needing to pre-load the data in Qlik. Pretty cool in any situation. But downright required in situations where there are reasons for the data to not egress out of ServiceNow. 

ServiceNow provides something called AI Agents, that are very similar to Qlik Answers, in that users are able to simply ask natural language questions about their data. You gotta LIKE that.

Also like Qlik Answers, ServiceNow AI Agents are able to be called via a well documented REST API. Which means you can consume those endpoints from within Qlik. You gotta LOVE that. 

Scenario

That capability provides tremendous value for our joint customers for so many scenarios. The one I will focus on in this article is regarding a Customer Success Manager working in a Qlik.

The Qlik application they utilize has lots and lots of data that they can do analytics with using traditional dashboarding and visualization. Of course they simply open Qlik Answers to ask questions of any data that is already loaded in the application. Assume for this scenario that the CSM is focusing on customer renewals for whatever product they might be selling. 

They come across an account that is due for renewals soon, they can see that Qlik Predict has predicted that the account is likely to churn, and has ranked their health very low. They can see the NPS scores for the account have dropped significantly. Oh boy, they need to turn that frown, upside down. 

Before they call the customer, they would also like to know if they have any outstanding trouble incidents/problems. 

Not hard to imagine this use case. Having access to that information provides vital insights that the CSM needs to know how to effectively communicate with the customer when they call. How they get access also matters. They could always stop their day job, working in Qlik, and go login to ServiceNow, become a master in filtering and find the incidents that are open for this specific customer. But with the handy dandy Qlik Sense extension called ServiceNow Agent Dream shared in this post they don't have to. They simply ask "Do they have any open incidents?" 

Scenario Demonstration

I've created a simple Next - Next - Finish type demonstration that allows you to see this scenario in action. You simply start the tour, and press Next when you are ready to advance through it. 

Walk through the CSM Demonstration

ServiceNow AI Agent Dream Setup

If your goal was simply understand the capability and the scenario so you know "what's possible" then you can stop reading. But if your goal is to actually try and get this dream capability up and running in your environment then please continue. The next link is a very similar demo where you simply press Next to advance through, that walks you through how to create the same ServiceNow AI Agent that I used in my scenario. 

Walk through creating a ServiceNow AI Agent

Now that you at least understand the capability it's time to dive into the 3 attachments for this post:

1. Incident_Intelligence_Agent_Guide.docx - This document will walk you through how to build the ServiceNow AI agent since you will need 1 in your environment to call. Please refer to ServiceNow help on the topic or your BFF Claude/ChatGPT for help should anything in your environment differ from mine. 

2. ServiceNowAgentDream_Setup_Guide.docx - This document will walk you through how to install the ServiceNow Agent Dream extension and then how to configure it. OAuth authentication is required for ServiceNow AI Agents, so I walk you through how to do that as well. 

3. ServiceNowAgentDream.zip - This is the Qlik Sense extension that you need to download and install in your Qlik Sense environment/tenant. 

This article describes how to connect Qlik Cloud Analytics to Starburst Galaxy using a Qlik Data Gateway - Direct Access and the Starburst ODBC driver. It covers gateway installation and registration, ODBC driver and DSN configuration on the gateway host, and data connection setup in Qlik Cloud. It is intended for Qlik Cloud tenants that need to query Starburst Galaxy catalogs directly from Qlik Cloud apps and scripts.

Content

• Architecture Overview
• Prerequisites
• Qlik Data Gateway - Direct Access Requirement
• Install the Starburst ODBC Driver on the Gateway Host
• Configure an ODBC DSN on the Gateway Host
• Install and Register the Qlik Data Gateway - Direct Access
• Create a Data Connection in Qlik Cloud
• Load Script Patterns
• Trino SQL Compatibility Notes
• Comparison: Qlik Cloud vs. Qlik Sense on Windows
• Troubleshooting
• Related Content and References

Architecture Overview

Qlik Cloud Analytics is a fully managed SaaS platform. Because Starburst Galaxy is not directly accessible from the Qlik Cloud infrastructure without network configuration, a Qlik Data Gateway - Direct Access must be deployed within the same network as, or with routable access to, the Starburst Galaxy cluster endpoint. The gateway acts as a secure proxy, relaying data load requests from Qlik Cloud to Starburst Galaxy over the ODBC connection configured on the gateway host.

The connection flow will look as follows:

Qlik Cloud tenant → Qlik Data Gateway (Direct Access) → Starburst ODBC DSN → Starburst Galaxy cluster

The gateway host is a Windows server that you manage. It must have outbound HTTPS access to both the Qlik Cloud tenant (port 443) and the Starburst Galaxy cluster endpoint (port 443).

Prerequisites

Before beginning, ensure the following requirements are met:

• A Qlik Cloud tenant with a Qlik Cloud Analytics subscription.
• Tenant Admin or Space Admin rights in Qlik Cloud to create data connections.
• A dedicated Windows host for the Qlik Data Gateway - Direct Access (minimum: 4 vCPU, 8 GB RAM, Windows Server 2016+).

  A Qlik Data Gateway - Direct Access must be installed and registered to your Qlik Cloud tenant before a Starburst ODBC data connection can be created or used. Attempting to create the connection without a registered gateway will result in an error.

• Network connectivity from the gateway host to the Starburst Galaxy cluster endpoint (port 443, HTTPS/TLS).
• Outbound HTTPS access (port 443) from the gateway host to your Qlik Cloud tenant URL (such as https://<tenant>.us.qlikcloud.com).
• A Starburst Galaxy service account with SELECT privileges on the target catalog and schema.
• Administrator access on the gateway host to install software and configure ODBC System DSNs.

Qlik Data Gateway - Direct Access Requirement

A Qlik Data Gateway - Direct Access is required to connect Qlik Cloud Analytics to Starburst Galaxy. All connections to on-premises or privately hosted data sources are routed through the gateway.

The gateway must be installed on a host that:

• Has network access to the Starburst Galaxy cluster on port 443.
• Has the Starburst ODBC driver installed and a System DSN configured (see Install the Starburst ODBC Driver on the Gateway Host, and Configure an ODBC DSN on the Gateway Host).
• Has outbound HTTPS access to the Qlik Cloud tenant on port 443.
• Runs continuously. The gateway must be active whenever a Qlik Cloud app or script loads data from Starburst.

For high availability, install the gateway on two or more hosts and register all of them to the same Qlik Cloud tenant. Qlik Cloud will distribute data load requests across available gateway instances.

Install the Starburst ODBC Driver on the Gateway Host

The Starburst ODBC driver must be installed on the gateway host. Qlik Cloud reads data through the gateway, so the driver must be present and configured where the gateway is running.

1. Download the Driver
   1. Log in to your Starburst Galaxy account at https://galaxy.starburst.io.
   2. Navigate to Settings > Clients & Tools > Drivers.
   3. Download the Windows 64-bit ODBC driver package (.msi or .zip) appropriate for the gateway host operating system.
   4. Copy the installer to the gateway host.
2. Install the Driver
   1. Run the installer as a local administrator on the gateway host.
   2. Accept the licence agreement and choose the default installation directory.
   3. When prompted, select System DSN scope so that the Qlik Data Gateway service account can access the driver.
   4. Complete the installation. No restart is required.

Install the 64-bit driver on the gateway host. The Qlik Data Gateway - Direct Access runs as a 64-bit process and requires the 64-bit ODBC driver. Use ODBC Data Source Administrator (64-bit) for all DSN configuration.

Configure an ODBC DSN on the Gateway Host

A System DSN must be created on the gateway host. This is the DSN that Qlik Cloud will reference when the data connection is used in a load script or app.

1. Open ODBC Data Source Administrator (64-bit) on the gateway host.
2. Click the System DSN tab, then click Add.
3. Select the Starburst ODBC Driver from the driver list and click Finish.
4. Configure the DSN with the following settings:
   
   

   Setting	Value
   DSN Name	StarburstGalaxy (must match the name used when creating the Qlik Cloud data connection)
   Host	<your-cluster>.galaxy.starburst.io
   Port	443
   Catalog	Leave blank (set per query or in the Qlik load script)
   Authentication	LDAP (username/password) or OAuth2 (token)
   SSL	Enabled (required for Galaxy)
   SSL Certificate	Use system certificate store

5. Click Test Connection to verify connectivity from the gateway host to Starburst Galaxy. A successful test returns the Starburst Galaxy version. 
6. Click OK to save the DSN.

Test the DSN connection while logged in as the same Windows service account that will run the Qlik Data Gateway service. DSN access permissions are per-user for User DSNs and per-machine for System DSNs. Always use System DSN for service accounts.

Install and Register the Qlik Data Gateway - Direct Access

The Qlik Data Gateway - Direct Access installer is downloaded from the Qlik Cloud Administration activity center and registers the gateway to your tenant during installation.

1. Download the Installer
   1. In Qlik Cloud, open the Qlik Cloud Administration activity center.
   2. Navigate to Data Gateways.
   3. Click Add and select Direct Access Gateway.
   4. Follow the on-screen instructions to download the installer for the gateway host operating system.
2. Install the Gateway
   1. Copy the installer to the gateway host.
   2. Run the installer as a local administrator.
   3. When prompted, enter the Qlik Cloud tenant URL and your API key.
      
      See Generating and managing API keys for instructions on how to generate an API key.
      
      
   4. Complete the installation. The gateway service will start automatically and register with the Qlik Cloud tenant.
3. Verify the Gateway is registered
   1. Return to the Qlik Cloud Administration activity center > Data Gateways.
   2. Confirm the gateway appears in the list with a Connected status.
      If the gateway shows a Disconnected status, check outbound HTTPS connectivity from the gateway host to the tenant URL on port 443.

The gateway service runs under a Windows service account. Ensure this account has Read access to the System DSN registry keys and is granted Log on as a service rights on Windows.

Create a Data Connection in Qlik Cloud

Once the gateway is registered and the ODBC DSN is configured on the gateway host, create the ODBC data connection in Qlik Cloud.

1. In Qlik Cloud, go to Create
2. Choose Data connection from the available actions and choose your Space
3. In the connector list, search for and select ODBC.
4. In the connection configuration panel, set the following:
   
   

   Field	Value
   Data gateway	Select the Direct Access Gateway registered in Install and Register the Qlik Data Gateway - Direct Access
   DSN	StarburstGalaxy (the System DSN configured on the gateway host in Configure an ODBC DSN on the Gateway Host)
   Username	Starburst Galaxy service account username
   Password	Starburst Galaxy service account password or personal access token
   Connection name	Data Nova Conference:Starburst Galaxy

5. Click Create.
6. Use the Test button to verify the connection. The test runs through the gateway, confirming end-to-end connectivity.

The connection name Data Nova Conference:Starburst Galaxy is the canonical name used in all Qlik load scripts for this integration. Changing it requires updating all dependent scripts. This name is consistent across Qlik Sense Enterprise on Windows and Qlik Cloud (this article).

Load Script Patterns

Load scripts in Qlik Cloud apps use the same patterns as Qlik Sense on Windows. The LIB CONNECT TO connection name must match the data connection created in Create a Data Connection in Qlik Cloud.

Establish the Connection

Always use the following statement at the top of the load script tab that accesses Starburst Galaxy:

LIB CONNECT TO 'Data Nova Conference:Starburst Galaxy'; 

Basic SQL SELECT

Use three-part table names (catalog.schema.table) in all Trino SQL statements:

Customers:
SQL SELECT
    customer_id,
    customer_name,
    region,
    created_date
FROM hive.sales.customers
WHERE created_date >= DATE '2024-01-01';

Joining Tables

Perform joins in SQL rather than in the Qlik data model to reduce data transfer volume through the gateway:

Orders:
SQL SELECT
    o.order_id,
    o.customer_id,
    o.order_date,
    o.total_amount,
    c.customer_name,
    c.region
FROM hive.sales.orders o
JOIN hive.sales.customers c ON o.customer_id = c.customer_id;

Incremental Load

Use Qlik variables to pass date parameters into the SQL predicate for incremental data loads:

LET vLastLoadDate = Date(Today()-1, 'YYYY-MM-DD');

Transactions:
SQL SELECT *
FROM hive.sales.transactions
WHERE transaction_date >= DATE '$(vLastLoadDate)';

Avoiding Synthetic Keys

Rename non-key fields that share names across tables by prefixing the table name. Island tables should be commented out:

Orders:
SQL SELECT
    order_id,
    customer_id, // Key — keep as-is
    order_date AS Order_order_date, // Renamed to avoid synthetic key
    total_amount AS Order_total_amount
FROM hive.sales.orders;

In Qlik Cloud, scheduled reloads run through the gateway. Ensure the gateway service is running and the gateway host has network access to Starburst Galaxy at the time scheduled reloads are triggered.

Trino SQL Compatibility Notes

Starburst Galaxy uses the Trino query engine. The following SQL conventions differ from standard ANSI SQL and must be observed in all Qlik load script SQL statements:

Comparison: Qlik Cloud vs. Qlik Sense on Windows

The table below summarises the key differences in the Starburst connection setup between Qlik Cloud Analytics and Qlik Sense Enterprise on Windows (client-managed):

Troubleshooting

Gateway shows Disconnected in Qlik Cloud

• Verify outbound HTTPS connectivity from the gateway host to the Qlik Cloud tenant URL on port 443.
• Check that the gateway service is running: in Windows Services, look for Qlik Data Gateway - Direct Access.
• Review the gateway log files at %ProgramData%\Qlik\DataGateway\logs for connection errors.
• Confirm the API key used during registration has not been revoked in Qlik Cloud.

Data connection test fails: DSN not found

• Confirm the DSN name in the Qlik Cloud data connection matches exactly (case-sensitive) the System DSN name on the gateway host.
• Open ODBC Data Source Administrator (64-bit) on the gateway host and verify the DSN exists under the System DSN tab.
• Ensure the Qlik Data Gateway service account has access to the System DSN. Restart the gateway service after creating or modifying the DSN.

Data connection test fails: SSL/TLS error

• Confirm that the Windows certificate store on the gateway host trusts the CA certificate chain for *.galaxy.starburst.io.
• The test connection runs on the gateway host, not in Qlik Cloud. All certificate issues must be resolved on the gateway host.

Load script error: [Starburst][Trino] Error executing query

• Verify the three-part table name is correct. Catalog, schema, and table names are case-sensitive.
• Confirm the Starburst Galaxy service account has SELECT privileges on the target table.
• Test the SQL directly in the Starburst Galaxy Query Editor before embedding it in the Qlik load script.

Scheduled reload fails, but manual reload succeeds

• Scheduled reloads run through the gateway under the service account context. Ensure the gateway service account has the same DSN access as the interactive user.
• Verify the gateway is in a Connected state at the time the reload is scheduled.
• Check the Qlik Cloud reload log for gateway timeout errors and increase the gateway connection timeout if necessary.

Slow reload performance

• Push filtering predicates into the SQL WHERE clause rather than relying on Qlik WHERE clauses. All data passes through the gateway, so minimising row count reduces transfer time.
• Select only required columns rather than using SELECT *.
• Consider co-locating the gateway host in the same network region as the Starburst Galaxy cluster to minimise latency.

Related Content and References

• Qlik Data Gateway - Direct Access documentation 
• Starburst Galaxy documentation 
• Qlik Cloud Data Sources

Environment

• Qlik Cloud

The Qlik Talend Studio job execution failed with code 1 and the error message:

Job stopped with errors or unable to run. Exception in thread "main" java.lang.NoClassDefFoundError: net/snowflake/client/loader/LoadResultListener

This indicates that Qlik Talend Studio could not find the required Snowflake client class during runtime.

Resolution

Replace the JAR with a fresh Snowflake JDBC driver (snowflake-jdbc.jar). 

See the following guides for details:

• Ways to install external modules 
• tLibraryLoad: Loads useable Java libraries in a Job

Cause

The error NoClassDefFoundError occurs when a Java class is missing from the runtime environment.

In this case, the Snowflake JAR file bundled with the older Qlik Talend Studio version did not include the LoadResultListener class, indicating a corrupted JAR file.

This mismatch between Qlik Talend Studio and the Snowflake connector causes the job to stop unexpectedly.

Environment

• Qlik Talend Studio

Although the Talend Remote Engine (RE) is paired correctly in the Qlik Talend Management Console, it repeatedly becomes unavailable. Re-pairing and restarting the Remote Engine only temporarily restored availability; the Remote Engine becomes unavailable again as soon as a job is executed and subsequently fails. 

Log snippet:

WARN  | pool-30-thread-1 | PairingAgent                     | 284 - org.talend.ipaas.engine.pairing.agent - 2.12.9 |  | Some bundles are not initialized. Cannot start EventSource ...
WARN  | pool-30-thread-1 | EngineBootChecker                | 278 - org.talend.ipaas.engine.container-common - 2.12.9 |  | vault-client state is Waiting  diag : Declarative Services
org.talend.observability.omc.appender.vault (18)

Resolution

That is a known challenge in the legacy 2.12.x version.

To resolve, append the following in re/etc/org.talend.observability.omc.appender.vault.cfg:

vault.timeRefreshBeforeExpiry=60
vault.path=engines
vault.max.retry=3
# retry interval in milliseconds
vault.retry.interval=1000
# in miliseconds
vault.request.timeout=5000

Environment

• Qlik Talend Cloud 
• Qlik Talend Management Console

Records with trailing character spaces are truncated by default to remove any trailing empty spaces. Any empty spaces in the front or back of the record are removed. If you have a record that is nothing but empty spaces, it will also be truncated to a null value record.

This can cause Not Null violation constraints on your target endpoint if the column is designated as a Not Null column type.

Resolution

On your source connection endpoint, add an internal parameter (A) keepCharTrailingSpaces (B) with the value of true (C), and save the connection.

If this parameter is not available for your endpoint, contact support for further instructions.

Example:

Cause

Empty spaces are truncated by default, which can lead to null values if the record was only empty spaces.

Internal Investigation ID(s)

• SUPPORT-10582

Environment

• Qlik Cloud Data Integration

This is a catch-all solution for PKIX path-building failures following the error:

sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

Linux

1. Obtain the certificate chain:
   
   openssl s_client -showcerts -connect <URL>:<PORT> </dev/null 2>/dev/null \ | awk '/BEGIN CERTIFICATE/{i++} {print > ("cert" i ".pem")}'
   
   
2. Import certificate(s) to truststore:
   
   keytool -importcert -alias <choose name> -file <cert file> -keystore <truststore path and filename> -trustcacerts

Windows

1. Obtain the certificate chain:
   
   openssl s_client -showcerts -connect <URL:<PORT> < NUL > chain.txt 2>NUL
   
   
2. Obtain certificates from the chain file:
   
   powershell -Command ^
   
    "$i=0;$in=$false;$b=@();foreach($l in Get-Content chain.txt){if($l-match 'BEGIN CERTIFICATE'){ $i++;$b=@();$in=$true } if($in){ $b+=$l } if($l-match 'END CERTIFICATE' -and $in){ $b|Set-Content -Encoding ascii ('cert'+$i+'.pem');$in=$false } }"
   
   
3. Import certificate(s) to truststore:
   
   keytool -importcert -alias <choose name> -file <cert file> -keystore <truststore path and filename> -trustcacerts

Example

• openssl s_client -showcerts -connect pair.us.cloud.talend.com:443 </dev/null 2>/dev/null \ | awk '/BEGIN CERTIFICATE/{i++} {print > ("cert" i ".pem")}'

• keytool -importcert -alias talend1 -file cert1.pem -keystore /opt/jdk/lib/security/cacerts -trustcacerts

   

Environment

• Qlik Talend Studio

The Qlik Download page or Qlik Ideation app do not show their expected content. The web page and browser console display error messages referring to HTTP 401 Unauthorized access, which may look similar to the below examples. 

• {"errors":[{"title":"State verification failed","detail":"State not valid, missing request forgery protection","code":"STATE-1","status":"401"}],"traceId":"{ID}"}
• VM624:1 GET https://download.us.qlikcloud.com/api/v1/users/me 401
• VM624:1 GET https://download.us.qlikcloud.com/api/v1/csrf-token?qlik-web-integration-id={ID} 401

Resolution

The Qlik Download page and Ideation App on Qlik Community require 3rd party cookies as part of the current web integration. The accessing browser must allow 3rd-party cookies while accessing the Qlik Downloads page in order for the page to render successfully. 

The browser does not have to completely allow 3rd party cookies, but can also just allow 3rd cookies for the *.qlik.com or community.qlik.com domain. 

The cookie settings are browser-specific, please consult browser help for more details. 

Cause

The Qlik Download page and Ideation App in Qlik Community are composed by an embedded object hosted in Qlik Cloud. This means cookies for the user session are associated with two different domains, community.qlik.com and qlikcloud.com. The browser refer to the parent page (community.qlik.com) as a 1st party cookie, while the embedded content from a different domain (qlikcloud.com) is referred to as a 3rd party cookie. 

3rd party cookies may be blocked in a browser as a mechanisms to block user tracking and advertisement. Browser incognito mode may also block 3rd party cookies by default as part of keeping the user more anonymous. 

Related Content

Clear, allow & manage cookies in Chrome 
Third-party cookies and Firefox tracking protection 
Microsoft Edge, browsing data, and privacy 
Clear cookies in Safari on Mac 

Qlik Talend Studio failed to install JAR files with the error:

Network is unavailable, please fix it

This occurred even though the machine had an active internet connection and the complete SSL certificate chain had been successfully imported.

Log Snippet:

javax.net.ssl.SSLHandshakeException: (certificate_unknown) PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target: https://talend-update.talend.com/nexus/content/groups/studio-libraries/

Resolution

Enable Windows long path support in the Windows registry:

Registry Change (long-path.reg):

Windows Registry Editor Version 5.00: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem]
"LongPathsEnabled"=dword:00000001

Alternatively, enable it using the Group Policy under Computer Configuration > Administrative Templates > System > Filesystem > Enable Win32 long paths

A system restart is required after the changes are applied.

Cause

The "Network is unavailable" error and the subsequent failure to install JAR files in Qlik Talend Studio are caused by the Windows long path limitation, rather than by network or SSL issues.

The following troubleshooting steps can be used to trace the conclusion:

1. SSL Verification: Imported all relevant certificates into the cacerts keystore and verified using: keytool -import -alias <alias_name> -keystore "%JAVA_HOME%/jre/lib/security/cacerts"
2. Connectivity Test: Ran a standalone, simple Java application to test the HTTPS connection to https://talend-update.talend.com. The connection was successful, confirming that SSL communication and certificates were functioning correctly.
3. Isolating the Issue: Suspecting Qlik Talend Studio corruption, a fresh instance was unzipped. During extraction, Windows threw a "Destination Path Too Long" warning. This revealed that the Windows maximum path length limitation (MAX_PATH) was causing Qlik Talend Studio components to malfunction and misreport the issue as a network failure.

Environment

• Qlik Talend Studio

A Qlik Talend job build failed due to an Avro IndexedRecord resolution error caused by a migration task inconsistency:

The type org.apache.avro.generic.IndexedRecord cannot be resolved. It is indirectly referenced from required type org.talend.codegen.enforcer.OutgoingSchemaEnforcer

Removing the NewTckSnowflakeMigrationTask entry from the migration_task.index file forces Qlik Talend to reprocess the migration.

After re-importing the job, the build completes successfully without errors.

Resolution

1. In the exported job, navigate to the .settings folder.
2. Open the file: .settings/migration_task.index
3. Search for the entry:
   org.talend.designer.core.generic.model.migration.NewTckSnowflakeMigrationTask
4. Remove the corresponding JSON object:

   {
     "id" : "org.talend.designer.core.generic.model.migration.NewTckSnowflakeMigrationTask",
     "breaks" : "8.0.1",
     "version" : "8.0.1",
     "status" : "ok"
   }

5. Save the file
6. Re-import the job into Qlik Talend Studio

Cause

The type org.apache.avro.generic.IndexedRecord cannot be resolved. It is indirectly referenced from the required type org.talend.codegen.enforcer.OutgoingSchemaEnforcer.

Internal Investigation ID(s):

• SUPPORT-8719

Environment

• Qlik Talend Studio

Are you looking to download your purchased Qlik Products or download a Trial? All supported on-premise Qlik Products can be downloaded from Qlik's Product Download Site.

To access the Download Site, you need an active QlikID. You will be able to see all products your account is eligible for.

Qlik's download are hosted on GitHub. If you are unable to access GitHub and do not have the possibility of enabling exceptions, start a chat with us and we will be able to help you.

You can access the Download Page directly here, or navigate to it from the Community Home page:

1. Open the Qlik Community
2. Click on Support
3. Select Product Downloads
   
   
   
   

This shows the download page with the Latest release and patch preselected.

1. Choose a different filter in (1) Show Releases if you are looking for older product versions. By default, only the Latest release and patch will be displayed. 
   
   
   
   
2. From here:
   
   
   1. choose your Product Category (Qlik Data Analytics, Qlik Data Integration, Search All),
   2. your Product,
   3. your Release,
   4. and Release Number.
   5. Then click the Download Link
      
      

Unsupported versions are not available for download. See Product Lifecycle for details on what versions have reached end of support. 

Alternatively, instead of selecting your product directly, you can also search all available columns:

1. Click the Magnifying Glass
2. Begin typing your search
3. Select the result
4. Confirm the result

If you encounter issues with the download site start a chat with us and we will be able to help you right away.

Click here for video transcript

Task crash failure with Oracle source endpoint after upgrading to Qlik Replicate 2025.11. The task may crash while loading different tables.

Resolution

Upgrade to a version of Qlik Replicate that includes the documented fix for RECOB-11316.

• 2025.11 SP04
• 2025.5 SP05 
• 2026.5 SP01 

Qlik Replicate patches can be made available before their official release. Contact Qlik Support for details.

Cause

Product Defect ID: RECOB-11316

In rare scenarios, an UPDATE operation on a compressed table with All Columns Supplemental Logging enabled may cause a replication task to crash when a Change Table, Transformation, or Log Stream is configured.

Information provided on this defect is given as is at the time of documenting. For up-to-date information, please review the most recent Release Notes or contact support with the ID RECOB-11316 for reference.

Environment

• Qlik Replicate

Qlik Replicate experiences target apply failures, table suspension, or errors related to NULL values being inserted into NOT NULL primary key columns.

Resolution

Upgrade to a version of Qlik Replicate that includes the documented fix for RECOB-11607.

• 2025.11 SP04
• 2025.5 SP05 
• 2026.5 SP01 

Qlik Replicate patches can be made available before their official release. Contact Qlik Support for details.

Cause

Product Defect ID: RECOB-11607

UPDATE operations on compressed rows could miss a primary key column value, resulting in a NULL value being applied to the target. This may cause table suspension or target apply failures when the affected column is defined as NOT NULL.

Information provided on this defect is given as is at the time of documenting. For up-to-date information, please review the most recent Release Notes or contact support with the ID RECOB-11607 for reference.

Environment

• Qlik Replicate

Qlik Cloud includes robust disaster recovery and backup mechanisms for active tenant data. See Adaptive high-availability infrastructure for details.

However, this does not mean data that has been deleted by the customer is being retained. Any intentionally or accidentally deleted Qlik Cloud data cannot be recovered by Qlik. See Qlik Cloud Analytics: Is it Possible to Recover a Deleted App or Sheet?

To prevent data loss, customers are responsible for implementing their own backup strategy for any content that may be removed. This includes apps, sheets, and spaces within the Qlik Cloud environment.

How to Back Up Qlik Cloud Apps

There are several ways to back up Qlik Cloud content:

• Qlik Automate
• Qlik CLI
• Qlik REST APIs
• Third-party solutions

Qlik Automate

Qlik Automate supports the creation of workflows that regularly back up apps within Qlik Cloud. These workflows can, for example, be configured to export apps to external storage, synchronize content between spaces, or integrate with version control systems.

Here are some helpful resources to get started:

• CI/CD pipelines for Qlik Sense apps with automations and GitHub
• How to export a Qlik Sense app without data to an Amazon S3 bucket and import an app from a file on Amazon S3
• How to export Qlik Sense Apps from source to a target shared space using Qlik Application Automation

These automations can be tailored to meet organizational backup requirements and integrated into broader content management strategies.

Qlik CLI

Qlik CLI enables app exports using command-line tools.

For more information regarding Qlik CLI, please see this introduction on the Qlik Developer Portal.

With Qlik CLI installed, the “qlik app export <appId> [flags]” command can be used to export an app. More information about the command and its available flags can be found on its Qlik Developer Portal page.

Qlik REST APIs

The public Qlik REST APIs can be used to build a more customized, local solution.

Using the POST /api/v1/apps/{appId}/export endpoint returns a "Location" header with the download URL for the exported app.

Third-party solutions

External tools that integrate with Qlik Cloud can also be used to back up apps. Please note that third-party solutions are not supported by Qlik Support.

Environment

• Qlik Cloud

The Qlik Sense on Windows Content Monitor is intended for Qlik Administrators. Its purpose is to monitor and analyze your Qlik Sense content, including app usage, resource consumption, and data sources. This helps with governance, optimization, and identifying unused content.

Requirements

• Platform: Qlik Sense Enterprise on Windows
• Version: November 2025 onwards 
• Availability: Bundled with installation from version November 2025 onwards
• If you are running previous versions of Qlik Sense Enterprise on Windows, the Content Monitor is also available on Qlik's Downloads page here: Content Monitor (download page)
  • This must be manually installed, and a weekly reload is recommended.
  • The downloaded version is supported from Qlik Sense version Feb 2020.

Core Documentation

All technical details can be found in the two attached documents. These are your primary resources.

Qlik Sense Content Monitor User Guide

• • What it covers: A detailed, sheet-by-sheet explanation of the entire app. It describes what every KPI, chart, and table means for sections like "Weekly Summary," "Snapshot," "Applications," "Sessions," "Task Executions," "File Inventory," and "Infrastructure."

  • Use Case: 

    • Guiding a customer on how to read and interpret the data.

    • Answering customer questions like, "What does the 'Session Concurrency' sheet show?" or "How do I read the 'File Inventory' sheet?"

  • See the attached Qlik Sense Content Monitor User Guide

Configuration Guide

• • What it covers: This is the primary guide for setup and reload issues. It contains:

    • Detailed definitions for all script parameters (e.g., vCentralNodeHostName, vVirtualProxyPrefix, vServerLogFolder).

    • Performance tuning options (e.g., vFileScanMaxDuration, vAppRetrievalLoop, exclusion lists).

    • A "Trial Mode" section is used for troubleshooting initial reload failures.

    • A "Troubleshooting" section.

  • Use Case:

    • New installations.

    • Troubleshootings.

    • Tuning performance for long reloads.

  • See the attached Qlik Sense Content Monitor Configuration Guide

Environment

• Qlik Sense Enterprise on Windows

The following release notes cover the Qlik PostgreSQL installer (QPI) version 1.2.0 to 2.1.0.

Content

• What's New
• 2.1.0 September 2025 Release Notes
• Known Limitations (2.1.0)
• 2.0.0 May 2025 Release Notes
• Known Limitations (2.0.0)
• 1.4.0 December 2023 Release Notes
• Known Limitations (1.4.0)
• 1.3.0 May 2023Release Notes
• Known Limitations (1.3.0)
• 1.2.0 Release Notes

What's New

• The PostgreSQL version used by QPI has been updated to 14.17
• An upgrade of an already upgraded external instance is now possible
• Support for an upgrade of the embedded 14.8 database was added
• Silent installs and upgrades are supported beginning with Qlik PostgreSQL Installer 1.4.0 and later. QPI can now be used with silent commands to install or upgrade the PostgreSQL database. (SHEND-973)

2.1.0 September 2025 Release Notes

Known Limitations (2.1.0)

• Rollback is not supported.
• The database size is not checked against free disk space before a backup is taken.
• Windows Server 2012 R2 does not support PostgreSQL 14.17. QPI cannot be used on Windows Server 2012 R2.
• QPI will only upgrade a PostgreSQL instance that only contains Qlik Sense Databases (QSR, SenseServices, QSMQ, Licenses, QLogs, etc.)

2.0.0 May 2025 Release Notes

Known Limitations (2.0.0)

• Rollback is not supported.
• The database size is not checked against free disk space before a backup is taken.
• Windows Server 2012 R2 does not support PostgreSQL 14.17. QPI cannot be used on Windows Server 2012 R2.
• QPI will only upgrade a PostgreSQL instance that only contains Qlik Sense Databases (QSR, SenseServices, QSMQ, Licenses, QLogs, etc.)

1.4.0 December 2023 Release Notes

Known Limitations (1.4.0)

• QB-24990: Cannot upgrade PostgreSQL if Qlik Sense was installed in a custom directory such as D:\Sense. See Qlik PostgreSQL Installer (QPI): No supported existing Qlik Sense PostgreSQL database found.
• Rollback is not supported.
• Database size is not checked against free disk space before a backup is taken.
• QPI can only upgrade bundled PostgreSQL database listening on the default port 4432. Using QPI to upgrade a standalone database or a database previously unbundled with QPI is not supported.
• Cannot migrate a 14.8 embedded DB to standalone
• Windows Server 2012R2 does not support PostgreSQL 14.8. QPI cannot be used on Windows Server 2012R2.

1.3.0 May 2023 Release Notes

The event payloads emitted by the Qlik Cloud webhooks service are changing. Qlik is replacing a legacy event format with a new cloud event format.

Any legacy events (such as anything not already cloud event compliant) will be updated to a temporary hybrid event containing both legacy and cloud event payloads. This will start on or after November 3, 2025.

Please consider updating your integrations to use the new fields once added.

A formal deprecation with at least a 6-month notice will be provided via the Qlik Developer changelog. After that period, hybrid events will be replaced entirely by cloud events.

Webhook automations in Qlik Automate will not be impacted at this time.

Events impacted by this migration

The webhooks service in Qlik Cloud enables you to subscribe to notifications when your Qlik Cloud tenant generates specific events.

At the time of writing, the following legacy events are available:

Any events not listed above will remain as-is, as they already adhere to the cloud event format.

How are events changing

Each event will change to a new structure. The details included in the payloads will remain the same, but some attributes will be available in a different location.

The changes being made:

• All new property names will be lowercase, which may cause some duplication of existing properties within the data object.
• The following properties or objects will be updated:
  • cloudEventsVersion is replaced by specversion. For most events this will be from cloudEventsVersion: 0.1 to specversion: 1.0+.
  • contentType is replaced by datacontentype to describe the media type of the data object.
  • eventId is replaced by id.
  • eventTime is replaced by time.
  • eventTypeVersion is not present in the future schema.
  • eventType is replaced by type.
  • extensions.actor is replaced by authtype and authclaims.
  • extensions.updates is replaced by data._updates
  • extensions.meta, and any other direct objects on extensions are replaced by equivalents in data where relevant.
  • The direct properties of the extensions object will be moved to the root and renamed to be lowercase if needed, such astenantId,userId,spaceId, etc.

Example: Automation created event

This is the current legacy payload of the automation created event:

{
  "cloudEventsVersion": "0.1",
  "source": "com.qlik/automations",
  "contentType": "application/json",
  "eventId": "f4c26f04-18a4-4032-974b-6c7c39a59816",
  "eventTime": "2025-09-01T09:53:17.920Z",
  "eventTypeVersion": "1.0.0",
  "eventType": "com.qlik.v1.automation.created",
  "extensions": {
    "ownerId": "637390ef6541614d3a88d6c3",
    "spaceId": "685a770f2c31b9e482814a4f",
    "tenantId": "BL4tTJ4S7xrHTcq0zQxQrJ5qB1_Q6cSo",
    "userId": "637390ef6541614d3a88d6c3"
  },
  "data": {
    "connectorIds": {},
    "containsBillable": null,
    "createdAt": "2025-09-01T09:53:17.000000Z",
    "description": null,
    "endpointIds": {},
    "id": "cae31848-2825-4841-bc88-931be2e3d01a",
    "lastRunAt": null,
    "lastRunStatus": null,
    "name": "hello world",
    "ownerId": "637390ef6541614d3a88d6c3",
    "runMode": "manual",
    "schedules": {},
    "snippetIds": {},
    "spaceId": "685a770f2c31b9e482814a4f",
    "state": "available",
    "tenantId": "BL4tTJ4S7xrHTcq0zQxQrJ5qB1_Q6cSo",
    "updatedAt": "2025-09-01T09:53:17.000000Z"
  }
}

This will be the temporary hybrid event for automation created:

{
// cloud event fields
  "id": "f4c26f04-18a4-4032-974b-6c7c39a59816",
  "time": "2025-09-01T09:53:17.920Z",
  "type": "com.qlik.v1.automation.created",
  "userid": "637390ef6541614d3a88d6c3",
  "ownerid": "637390ef6541614d3a88d6c3",
  "tenantid": "BL4tTJ4S7xrHTcq0zQxQrJ5qB1_Q6cSo",
  "description": "hello world",
  "datacontenttype": "application/json",
  "specversion": "1.0.2",

// legacy event fields
  "eventId": "f4c26f04-18a4-4032-974b-6c7c39a59816",
  "eventTime": "2025-09-01T09:53:17.920Z",
  "eventType": "com.qlik.v1.automation.created",
  "extensions": {
    "userId": "637390ef6541614d3a88d6c3",
    "spaceId": "685a770f2c31b9e482814a4f",
    "ownerId": "637390ef6541614d3a88d6c3",
    "tenantId": "BL4tTJ4S7xrHTcq0zQxQrJ5qB1_Q6cSo",
  },
  "contentType": "application/json",
  "eventTypeVersion": "1.0.0",
  "cloudEventsVersion": "0.1",
  
// unchanged event fields
  "data": {
    "connectorIds": {},
    "containsBillable": null,
    "createdAt": "2025-09-01T09:53:17.000000Z",
    "description": null,
    "endpointIds": {},
    "id": "cae31848-2825-4841-bc88-931be2e3d01a",
    "lastRunAt": null,
    "lastRunStatus": null,
    "name": "hello world",
    "ownerId": "637390ef6541614d3a88d6c3",
    "runMode": "manual",
    "schedules": {},
    "snippetIds": {},
    "spaceId": "685a770f2c31b9e482814a4f",
    "state": "available",
    "tenantId": "BL4tTJ4S7xrHTcq0zQxQrJ5qB1_Q6cSo",
    "updatedAt": "2025-09-01T09:53:17.000000Z"
  },
  "source": "com.qlik/automations"
}

Timeline

• November 3, 2025: Hybrid events start emitting (combined legacy and cloud event payloads).
• At least 6 months after a formal deprecation notice: Legacy fields will be removed, leaving fully cloud events only.

Environment

• Qlik Cloud
• Qlik Cloud Government

This template was updated on December 4th, 2025 to replace the original installer and API key rotator with a new, unified deployer automation. Please disable or delete any existing installers, and create a new automation, picking the Qlik Cloud monitoring app deployer template from the App installers category.

Installing, upgrading, and managing the Qlik Cloud Monitoring Apps has just gotten a whole lot easier! With a single Qlik Automate template, you can now install and update the apps on a schedule with a set-and-forget installer using an out-of-the-box Qlik Automate template. It can also handle API key rotation required for the data connection, ensuring the data connection is always operational.

Some monitoring apps are designed for specific Qlik Cloud subscription types. Refer to the compatibility matrix within the Qlik Cloud Monitoring Apps repository.

'Qlik Cloud Monitoring Apps deployer' template overview

This automation template is a set-and-forget template for managing the Qlik Cloud Monitoring Applications, including but not limited to the App Analyzer, Entitlement Analyzer, Reload Analyzer, and Access Evaluator applications. Leverage this automation template to quickly and easily install and update these or a subset of these applications with all their dependencies. The applications themselves are community-supported; and, they are provided through Qlik's Open-Source Software (OSS) GitHub and thus are subject to Qlik's open-source guidelines and policies.

For more information, refer to the GitHub repository.

Features

• Can install/upgrade all or select apps.
• Can create or leverage existing spaces.
• Programmatically verified prerequisite settings, roles, and entitlements, notifying the user during the process if changes in configuration are required, and why.
• Installs latest versions of specified applications from Qlik’s OSS GitHub.
• Creates required API key.
• Creates required analytics data connection.
• Creates a daily reload schedule.
• Reload applications post-install.
• Tags apps appropriately to track which are installed and their respective versions.
• Supports both user and capacity-based subscriptions.

Configuration:

Update just the configuration area to define how the automation runs, then test run, and set it on a weekly or monthly schedule as desired.

Configure the run mode of the template using 7 variable blocks

Users should review the following variables:

1. configuredMonitoringApps: contains the list of the monitoring applications which will be installed and maintained. Delete any applications not required before running (default: all apps listed).
2. refreshConnectorCredentials: determines whether the monitoring application REST connection and associated API key will be regenerated every run (default: true).
3. reloadNow: determines whether apps are reloaded immediately following updates (default: true).
4. reloadScheduleHour: determines at which hour of the day the apps reload at for the daily schedule in UTC timezone (default: 06)
5. sharedSpaceName: defines the name of the shared space used to import the apps into prior to publishing. If the space doesn't exist, it'll be created. If the space exists, the user will be added to it with the required permissions (default: Monitoring - staging).
6. managedSpaceName: defines the name of the managed space the apps are published into for consumption/ alerts/ subscription use.If the space doesn't exist, it'll be created. If the space exists, the user will be added to it with the required permissions (default: Monitoring).
7. versionsToKeep: determines how many versions of each staged app is kept in the shared space. If set to 0, apps are deleted after publishing. If a positive integer value other than 0, that many apps will be kept for each monitoring app deployed (default: 0).

App management:

If the monitoring applications have been installed manually (i.e., not through this automation), then they will not be detected as existing. The automation will install new copies side-by-side. Any subsequent executions of the automation will detect the newly installed monitoring applications and check their versions, etc. This is due to the fact that the applications are tagged with "QCMA - {appName}" and "QCMA - {version}" during the installation process through the automation. Manually installed applications will not have these tags and therefore will not be detected.

FAQ

Q: Can I re-run the installer to check if any of the monitoring applications are able to be upgraded to a later version?

A: Yes. The automation will update any managed apps that don't match the repository's manifest version.

Q: What if multiple people install monitoring applications in different spaces?

A: The template scopes the application's installation process to a managed space. It will scope the API key name to `QCMA – {spaceId}` of that managed space. This allows the template to install/update the monitoring applications across spaces and across users. If one user installs an application to “Space A” and then another user installs a different monitoring application to “Space A”, the template will see that a data connection and associated API key (in this case from another user) exists for that space already. It will install the application leveraging those pre-existing assets.

Q: What if a new monitoring application is released? Will the template provide the ability to install that application as well?

A: Yes, but an update of the template from the template picker will be required, since the applications are hard coded into the template. The automation will begin to fail with a notification an update is needed once a new version is available.

Q:I have updated my application, but I noticed that it did not preserve the history. Why is that?

A: Each upgrade may generate a new set of QVDs if the data models for the applications have changed due to bug fixes, updates, new features, etc. The history is preserved in the prior versions of the application’s QVDs, so the data is never deleted and can be loaded into the older version. 

Qlik Sense Enterprise on Windows August 2023 has introduced support for parquet files. Support for parquet files is enabled by default but is only valid for newly generated apps.

This article guides you through enabling parquet file support for existing apps.

Resolution

To enable parquet files, they will need to be allowed as sources. We will use QlikSenseCLI in our example.  QlikSenseCLI is shipped with Qlik Sense Enterprise on Windows since May 2023. 

1. Open Powershell ISE as administrator
   
   
2. Import the QlikSenseCLI module in the current Powershell session:
   
   
   1. Open the script C:\Program Files\Qlik\Sense\Tools\qlik-installation-tools
   2. Run ImportQlikSenseCLIModule.ps1
   3. This will print an about API output on successful run:
      
      SchemaPath : About
      BuildVersion : 31.34.0.0
      BuildDate : 6/13/2023 10:08:17 AM
      DatabaseProvider : Devart.Data.PostgreSql
      NodeType : Central
      SharedPersistence : True
      RequiresBootstrap : False
      SingleNodeOnly : False
      ExtensionData :
      
      
3. Run the Parquet Whitelist Script:
   
   AddParquetExtentionWhitelistTable.ps1

You can now use parquet files in existing apps.

Environment

Qlik Sense Enterprise for Windows August 2023 and later

Enabling Data Analysis as a user who was assigned a custom role designed for Qlik Answers (Legacy) fails with:

Scope insight-advisor:experience does not exist or is not available on your tenant
Error code: IDENTITIES-10504

Resolution

Create a new custom role for Agentic Qlik Answers.

In Permissions:

1. Expand Features and Actions
2. Set Data analysis and Insights feed to Allowed 
   
   

Assign the new role to the users or groups who need to use Qlik Answers. Delete the old role if it is no longer needed. 

Cause

Custom Roles created for legacy Qlik Answers rather than the new Agentic Qlik Answers have different role permissions settings on the back end. Newly created custom roles will not run into the same permission issues as Legacy Qlik Answers.

Environment

• Qlik Answers
• Qlik Cloud