Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Qlik offers a wide range of channels to assist you in troubleshooting, answering frequently asked questions, and getting in touch with our technical experts. In this article, we guide you through all available avenues to secure your best possible experience.
For details on our terms and conditions, review the Qlik Support Policy.
Index:
We're happy to help! Here's a breakdown of resources for each type of need.
| Support | Professional Services (*) | |
| Reactively fixes technical issues as well as answers narrowly defined specific questions. Handles administrative issues to keep the product up-to-date and functioning. | Proactively accelerates projects, reduces risk, and achieves optimal configurations. Delivers expert help for training, planning, implementation, and performance improvement. | |
|
|
(*) reach out to your Account Manager or Customer Success Manager
Your first line of support: https://community.qlik.com/
Looking for content? Type your question into our global search bar:
Leverage the enhanced and continuously updated Knowledge Base to find solutions to your questions and best practice guides. Bookmark this page for quick access!
Subscribe to maximize your Qlik experience!
The Support Updates Blog
The Support Updates blog delivers important and useful Qlik Support information about end-of-product support, new service releases, and general support topics. (click)
The Qlik Design Blog
The Design blog is all about product and Qlik solutions, such as scripting, data modelling, visual design, extensions, best practices, and more! (click)
The Product Innovation Blog
By reading the Product Innovation blog, you will learn about what's new across all of the products in our growing Qlik product portfolio. (click)
Q&A with Qlik
Live sessions with Qlik Experts in which we focus on your questions.
Techspert Talks
Techspert Talks is a free webinar to facilitate knowledge sharing held on a monthly basis.
Technical Adoption Workshops
Our in depth, hands-on workshops allow new Qlik Cloud Admins to build alongside Qlik Experts.
Qlik Fix
Qlik Fix is a series of short video with helpful solutions for Qlik customers and partners.
Suggest an idea, and influence the next generation of Qlik features!
Search & Submit Ideas
Ideation Guidelines
Get the full value of the community.
Register a Qlik ID:
Incidents are supported through our Chat, by clicking Chat Now on any Support Page across Qlik Community.
To raise a new issue, all you need to do is chat with us. With this, we can:
Log in to manage and track your active cases in the Case Portal. (click)
Before you can access the Support Portal, please complete your Community account setup. See First time access to the Qlik Customer Support Portal fails with: Unauthorized Access Please try signing out and sign in again.
Please note: to create a new case, it is easiest to do so via our chat (see above). Our chat will log your case through a series of guided intake questions.
When creating a case, you will be prompted to enter problem type and issue level. Definitions shared below:
Select Account Related for issues with your account, licenses, downloads, or payment.
Select Product Related for technical issues with Qlik products and platforms.
If your issue is account related, you will be asked to select a Priority level:
Select Medium/Low if the system is accessible, but there are some functional limitations that are not critical in the daily operation.
Select High if there are significant impacts on normal work or performance.
Select Urgent if there are major impacts on business-critical work or performance.
If your issue is product related, you will be asked to select a Severity level:
Severity 1: Qlik production software is down or not available, but not because of scheduled maintenance and/or upgrades.
Severity 2: Major functionality is not working in accordance with the technical specifications in documentation or significant performance degradation is experienced so that critical business operations cannot be performed.
Severity 3: Any error that is not Severity 1 Error or Severity 2 Issue. For more information, visit our Qlik Support Policy.
If you require a support case escalation, you have two options:
When other Support Channels are down for maintenance, please contact us via phone for high severity production-down concerns.
A collection of useful links.
Qlik Cloud Status Page
Keep up to date with Qlik Cloud's status.
Support Policy
Review our Service Level Agreements and License Agreements.
Live Chat and Case Portal
Your one stop to contact us.
From R2024-05, Java 17 will become the only supported version to start most Talend modules, enforcing the improved security of Java 17 and eliminating concerns about Java's end-of-support for older versions. In 2025, Java 17 will become the only supported version for all operations in Talend modules.
Starting from v2.13, Talend Remote Engine requires Java 17 to run. If some of your artifacts, such as Big Data Jobs, require other Java versions, see Specifying a Java version to run Jobs or Microservices.
Content
| Qlik Talend Module | Patch Level and Version |
| Studio | Supported from R2023-10 onwards |
| Remote Engine | 2.13 or later |
| Runtime | 8.0.1-R2023-10 or later |
For Windows users, please follow the JDK installation guide (docs.oracle.com).
For Linux users, please follow the JDK installation guide (docs.oracle.com).
For MAC OS users, please follow the JDK installation guide (docs.oracle.com).
When working with software that supports multiple versions of Java, it's important to be able to specify the exact Java version you want to use. This ensures compatibility and consistent behavior across your applications. Here is how you can specify a specific Java version on the following products (such as build servers, shared application server, and similar):
For Studio users who are using multiple JDKs, please follow the appropriate instructions listed above and follow the proceeding additional steps:
-vm
<JDK17 HOME>\bin\server\jvm.dll
For Remote Engine (RE) users who are using multiple JDKs, please follow the appropriate instructions listed above and follow the proceeding additional steps.
For Runtime users who are using multiple JDKs, please follow the appropriate instructions listed above and follow the proceeding additional steps.
If Runtime is not running as a service:
With the Enable Java 17 compatibility option activated, any Job built by Talend Studio cannot be executed with Java 8. For this reason, verify the Java environment on your Job execution servers before activating the option.
To use Talend Administration Center with Java 17, you need to open the <tac_installation_folder>/apache-tomcat/bin/setenv.sh file and add the following commands:
# export modules export JAVA_OPTS="$JAVA_OPTS --add-opens=java.base/sun.security.x509=ALL-UNNAMED --add-opens=java.base/sun.security.pkcs=ALL-UNNAMED"
Windows users use <tac_installation_folder>\apache-tomcat\bin\setenv.bat
Follow the steps below to configure the JobServer to use the new Java version.
Navigate to the JobServer Configuration:
Go to the <JobServerRootDir>\conf directory, where <JobServerRootDir> is the path to your Talend JobServer installation.
Open the Configuration File for Editing:
Locate the TalendJobServer.properties file and open it with a text editor of your choice.
Set the Java 17 Executable Path:
Find the line dedicated to the Job launcher path within the file. You will modify this line to point to the Java 17 executable.
org.talend.remote.jobserver.commons.config.JobServerConfiguration.JOB_LAUNCHER_PATH="C:\\Program Files\\Java\\jdk-17\\bin\\java.exe"
org.talend.remote.jobserver.commons.config.JobServerConfiguration.JOB_LAUNCHER_PATH=/usr/lib/jvm/java-17-openjdk/bin/java
Replace the example paths with the actual path where Java 17 is installed on your system. Ensure to point directly to the Java executable within the bin directory of your JDK installation.
Save Your Changes:
After editing, save the TalendJobServer.properties file.
Restart Talend JobServer:
For the changes to take effect, restart your Talend JobServer.
After completing these steps, Talend JobServer will utilize Java 17 for executing Jobs, ensuring compatibility with the latest Java version supported by Talend modules.
For Java 17 users, Talend CICD process requires the following Maven options:
set "MAVEN_OPTS=%MAVEN_OPTS% --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/sun.security.x509=ALL-UNNAMED --add-opens=java.base/sun.security.pkcs=ALL-UNNAMED"
For Java 17 users, Talend CICD process requires the following Maven options:
export MAVEN_OPTS="$MAVEN_OPTS \ --add-opens=java.base/java.net=ALL-UNNAMED \ --add-opens=java.base/sun.security.x509=ALL-UNNAMED \ --add-opens=java.base/sun.security.pkcs=ALL-UNNAMED"
<name>TALEND_CI_RUN_CONFIG</name> <description>Define the Maven parameters to be used by the product execution, such as: - Studio location - debug flags These parameters will be put to maven 'mavenOpts'. If Jenkins is using Java 17, add: --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/sun.security.x509=ALL-UNNAMED --add-opens=java.base/sun.security.pkcs=ALL-UNNAMED </description>
Overview
Enable your Remote Engine to run Jobs or Microservices using a specific Java version.
By default, a Remote Engine uses the Java version of its environment to execute Jobs or Microservices. With Remote Engine v2.13 and onwards, Java 17 is mandatory for engine startup. However, when it comes to running Jobs or Microservices, you can specify a different Java version. This feature allows you to use a newer engine version to run the artifacts designed with older Java versions, without the need to rebuild these artifacts, such as the Big Data Jobs, which reply on Java 8 only.
When developing new Jobs or Microservices that do not exclusively rely on Java 8, that is to say, they are not Big Data Jobs, consider building them with the add-opens option to ensure compatibility with Java 17. This option opens the necessary packages for Java 17 compatibility, making your Jobs or Microservices directly runnable on the newer Remote Engine version, without having to go through the procedure explained in this section for defining a specific Java version. For further information about how to use this add-opens option and its limitation, see Setting up Java in Talend Studio.
Procedure
c:\\Program\ Files\\Java\\jdk11.0.18_10\\bin\\java.exe
org.talend.remote.jobserver.commons.config.JobServerConfiguration.JOB_LAUNCHER_PATH=c:\\jdks\\jdk11.0.18_10\\bin\\java.exe
ms.custom.jre.path=C\:/Java/jdk/binMake this modification before deploying your Microservices to ensure that these changes are correctly taken into account.
For Java Option Command --add-opens, using SPACE or = depends on OS, JDK version or the place where you setup, there are 3 cases:
1. support both SPACE and =
2. support SPACE only
3. support = only
Example:
--add-opens=java.base/java.net=ALL-UNNAMED
--add-opens java.base/java.net=ALL-UNNAMED
QPI does not currently support PostgreSQL 18. See Qlik Sense Enterprise on Windows: How to manually unbundle the Qlik Sense Repository Database to PostgreSQL 18 for a manual method to unbundle your PostgreSQL instance and upgrade it to PostgreSQL 18.
In this article, we walk you through the requirements and process of how to upgrade and unbundle an existing Qlik Sense Repository Database (see supported scenarios) as well as how to install a brand new Repository based on PostgreSQL. We will use the Qlik PostgreSQL Installer (QPI).
For a manual method, see How to manually upgrade the bundled Qlik Sense PostgreSQL version to 12.5 version.
Using the Qlik Postgres Installer not only upgrades PostgreSQL; it also unbundles PostgreSQL from your Qlik Sense Enterprise on Windows install. This allows for direct control of your PostgreSQL instance and facilitates maintenance without a dependency on Qlik Sense. Further Database upgrades can then be performed independently and in accordance with your corporate security policy when needed, as long as you remain within the supported PostgreSQL versions. See How To Upgrade Standalone PostgreSQL.
Index
Video Walkthrough
Video chapters:
The following versions have been tested and verified to work with QPI:
Qlik Sense February 2022 to Qlik Sense November 2024.
If you are on a Qlik Sense version prior to these, upgrade to at least February 2022 before you begin.
Qlik Sense November 2022 and later do not support 9.6, and a warning will be displayed during the upgrade. From Qlik Sense August 2023 a upgrade with a 9.6 database is blocked.
The Qlik PostgreSQL Installer supports installing a new standalone PostgreSQL database with the configurations required for connecting to a Qlik Sense server. This allows setting up a new environment or migrating an existing database to a separate host.
Using the Qlik PostgreSQL Installer on a patched Qlik Sense version can lead to unexpected results. If you have a patch installed, either:
Do not use the standard Qlik Sense folders, such as C:\Program Files\Qlik\Sense\Repository\PostgreSQL\ and C:\Programdata\Qlik\Sense\Repository\PostgreSQL\.
Do not use the standard Qlik Sense folders, such as C:\Program Files\Qlik\Sense\Repository\PostgreSQL\ and C:\Programdata\Qlik\Sense\Repository\PostgreSQL\.
Download the installer here.
Qlik PostgreSQL installer Release Notes
The following versions have been tested and verified to work with QPI (1.4.0):
February 2022 to November 2023.
If you are on any version prior to these, upgrade to at least February 2022 before you begin.
Qlik Sense November 2022 and later do not support 9.6, and a warning will be displayed during the upgrade. From Qlik Sense August 2023 a 9.6 update is blocked.
Uninstall the old Qlik Sense Repository Database service.
This step is required. Failing to remove the old service will lead the upgrade or patching issues.
Failing to reinstall the binaries will lead to errors when executing any number of service configuration scripts.If you do not immediately upgrade:
If the upgrade was unsuccessful and you are missing data in the Qlik Management Console or elsewhere, contact Qlik Support.
Now that your PostgreSQL instance is no longer connected to the Qlik Sense Enterprise on Windows services, all future updates of PostgreSQL are performed independently of Qlik Sense. This allows you to act in accordance with your corporate security policy when needed, as long as you remain within the supported PostgreSQL versions.
Your PostgreSQL database is fully compatible with the official PostgreSQL installers from https://www.enterprisedb.com/downloads/postgres-postgresql-downloads.
See How To Upgrade Standalone PostgreSQL, which documents the upgrade procedure for either a minor version upgrade (example: 14.5 to 14.8) or a major version upgrade (example: 12 to 14). Further information on PostgreSQL upgrades or updates can be obtained from Postgre directly.
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support. The video in this article was recorded in a earlier version of QPI, some screens might differ a little bit.
Qlik PostgreSQL installer version 1.3.0 Release Notes
Techspert Talks - Upgrading PostgreSQL Repository Troubleshooting
Backup and Restore Qlik Sense Enterprise documentation
Migrating Like a Boss
Optimizing Performance for Qlik Sense Enterprise
Qlik Sense Enterprise on Windows: How To Upgrade Standalone PostgreSQL
How-to reset forgotten PostgreSQL password in Qlik Sense
How to configure Qlik Sense to use a dedicated PostgreSQL database
Troubleshooting Qlik Sense Upgrades
This document is a general guide and is provided as is. Modifications to the process may be necessary depending on your individual database setup.
If you have installed a standalone PostgreSQL database, or if you have used the Qlik PostgreSQL Installer (QPI) to upgrade and decouple your previously bundled database, then you can upgrade PostgreSQL at any time. This means you control maintenance and can immediately react to potential PostgreSQL security concerns by upgrading to a later service release or a later major version.
Content
This document covers the following scenario:
Run a complete backup of Qlik Sense Enterprise on Windows site as described in Backup and restore Qlik Sense Enterprise on Windows.
These steps apply if you are upgrading within a major PostgreSQL release (example: 14.5 to 14.8).
No further steps are required.
If you are moving to a higher major version, an in-place upgrade will not be possible. Instead, we will install the the new version in parallel, then then migrate the old database and eventually uninstall the old version. Our example is written using PostgreSQL 12 to 14.
Upgrading and unbundling the Qlik Sense Repository Database using the Qlik PostgreSQL Installer
How to manually upgrade the bundled Qlik Sense PostgreSQL version to 12.5 version
Changing the Database Superuser Password without Qlik Sense Installed
Qlik DataTransfer is deprecated. Support ended on April 30, 2026, and the product is expected to stop working after November 29, 2026. The recommended replacement is Qlik Data Gateway – Direct Access, as described in the Qlik DataTransfer Deprecation Notice for 2026.
This article covers cases where Qlik Data Gateway – Direct Access is not an option because data files, such as QVD files, must be produced in Qlik Sense Enterprise on Windows and then moved to Qlik Cloud. It shows how to replace Qlik DataTransfer with qlik-cli, the Qlik command-line interface, and a small script.
This article includes two attachments:
All information in this article is provided as-is and not supported by Qlik. If you need more direct assistance in implementing an alternative to Qlik Data Gateway - Direct Access, connect with your peers on Qlik Community or contact Qlik Professional Services.
Content
Qlik DataTransfer performed four tasks, which a replacement needs to cover:
A replacement also needs authentication that can be rotated, a schedule, logs that show what succeeded, and a plan for files that are still being written. All of this can be built by wrapping qlik-cli in a script.
Start with one question: can the reload run entirely in Qlik Cloud?
If it can, use Qlik Data Gateway – Direct Access. The gateway lets Qlik Cloud apps reach sources behind your firewall securely, without opening inbound ports, so the reload runs in Qlik Cloud against the source itself. There are no files to move or keep in sync, and nothing to schedule and monitor on a server.
The deprecation notice names the File connector, the REST connector, and the generic ODBC connector through Direct Access as the options for feature parity with Qlik DataTransfer.
Use qlik-cli to move files only when that is not possible. Typical reasons:
qlik context create my-tenant --server https://my-tenant.eu.qlikcloud.com --api-key <API-KEY>
qlik context use my-tenant
qlik space ls
An API key carries the full permissions of the user who created it and cannot be scoped. Alternatively, a qlik-cli context can use an OAuth machine-to-machine client, which runs as a bot user; the contexts page covers both.
If qlik space ls shows your spaces, you are connected. The key stays in the qlik-cli context, so it never needs to live in your scripts.
Each space has a DataFiles connection (data-file connection ls), and you upload to that connection with data-file create. The -q flag returns just the id:
qlik space ls --name <space-name> -q # space id returned
qlik data-file connection ls --spaceId <space-id> -q # connection id returned
qlik data-file create --connectionId <connection-id> --name <space-file-name> --file <local-path-to-file>
That is the whole upload. The file is now under Data Files in the space.
For large files or unreliable networks, add two flags and let qlik-cli do the work:
qlik data-file create --connectionId <connection-id> --name <space-file-name> --file <local-path-to-file> --resumable --retry 3 --interval 5
The same operations are available as the Data files REST API if you ever need them outside the CLI.
A / in --name is a folder separator, and missing folders are created. To mirror a local folder tree, use each file’s relative path as its name:
qlik data-file create --connectionId <connection-id> --name sales/2026/q1/orders.qvd --file D:\QlikData\Sales\2026\q1\orders.qvd
Running create a second time fails with a 409 Conflict, because the file already exists. To replace an existing file:
qlik data-file ls --connectionId <connection-id> --name sales/2026/q1/orders.qvd -q # file id returned
qlik data-file update <file-id> --connectionId <connection-id> --name sales/2026/q1/orders.qvd --file D:\QlikData\Sales\2026\q1\orders.qvd
Searching by the full path with --name is the reliable way to find a file. A plain ls returns only the first 20 items unless you add --limit.
Looking up each file in a folder, then creating or updating it, is a loop. Python’s subprocess module is enough, because qlik-cli handles authentication, chunked uploads (--resumable), and retries (--retry), so the script needs no retry logic of its own. The core of the example script 01_upload_folder.py is:
for path in sorted(source.rglob("*.qvd")):
name = path.relative_to(source).as_posix() # keeps the folder structure
file_id = qlik("data-file", "ls", "--connectionId", connection_id, "--name", name, "-q")
if file_id:
qlik("data-file", "update", file_id, ..., "--resumable", "--retry", "3")
else:
qlik("data-file", "create", ..., "--resumable", "--retry", "3")
To run the script on a schedule, use either:
Uploading every file every night is wasteful and forces a Qlik Cloud reload nightly.
The example script 02_upload_changed.py keeps a small state file with the size, modified time, and SHA-256 hash of each file. Size and time are a cheap first check, and the hash catches files that were rewritten with identical content. The script then knows whether anything changed, which decides whether the Qlik Cloud apps need to reload.
If an on-premises reload is still writing orders.qvd when the script runs, the script can upload a half-written file. Choose one of the following strategies:
The 02_upload_changed.py example uses the simplest form of the last strategy: a file modified within the last 30 seconds is logged as LOCKED and left for the next run.
In the qvd-upload example, this is the marker strategy in its quiet-period mode (stable_seconds, default 30). The default strategy there is skip, and you pick another per task in the configuration.
Note that this locking retry is about a file that is still being written. It is separate from the --retry flag, which retries a failed network request.
Before uploading, you may want the on-premises reload to run first. You can drive Qlik Sense Enterprise on Windows from qlik-cli in much the same way as Qlik Cloud: follow Using qlik-cli with Qlik Sense Enterprise client-managed (QRS) to set up a JWT virtual proxy, add a second context for the Windows server, and start the reload task with the qlik qrs commands:
qlik context create onprem --server https://<sense-server>/jwt --server-type windows --api-key <JWT>
qlik qrs task start by-name --name "Reload Sales data" --context onprem
The execution-result and task-status commands (qlik qrs --help lists them) let the script wait until the task has finished before the upload begins. The --context flag switches between the two environments, so one script can run both sides.
This needs qlik-cli 1.5.0 or later, and --insecure is only for a test server with a self-signed certificate.
After uploading, reload the Qlik Cloud apps that use the files, but only if something changed, with reload create and reload get (see also the Reloads REST API
qlik reload create --appId <app-id> -q # returns the reload id
qlik reload get <reload-id> # poll until it finishes
Write one line per file with a clear outcome, tagged with a run ID, plus a summary and an exit code the scheduler can act on.
This makes it possible to answer “what happened to file X?”:
INFO [a1b2c3d4] [sales] UPLOADED sales/2026/q1/orders.qvd (48211904 bytes)
INFO [a1b2c3d4] [sales] UNCHANGED sales/2026/q1/customers.qvd
WARNING [a1b2c3d4] [sales] LOCKED sales/2026/q1/big.qvd: modified 4s ago
INFO [a1b2c3d4] [sales] cloud reload app 5c0e...: SUCCEEDED
The qvd-upload zip file combines all of these pieces: configuration in YAML instead of code, several tasks per config, a dry run, all four locking strategies, and the on-premises and Qlik Cloud reloads. Uploads use qlik-cli's own --resumable and --retry (the retry count is qlik.retries in the configuration).
qvd-upload validate
qvd-upload run --dry-run
qvd-upload run
qvd-upload is an example, not a supported product. Use it as a starting point, and adapt it to your requirements.
qlik context update <name> --api-key <KEY>
In Qlik Talend Data Integration, users who have access to a data space through group membership do not receive email notifications for pipeline task events.
The following behavior was observed:
Users added directly to the space receive task notifications as expected.
Users who access the same space through a group do not receive notifications.
Email notifications are enabled at the tenant level, and tenant administrators can successfully send test emails.
The issue affects notification delivery rather than task execution.
This is a documented Qlik Cloud notification limitation, rather than an issue with the configured email provider.
Add affected users directly to the Qlik Cloud data space.
Sign in to Qlik Cloud with an account authorized to manage space members.
Navigate to the data space containing the affected pipeline tasks.
Open Space settings > Members.
Add the affected users individually with the appropriate space roles.
Ask each user to open their profile settings and confirm that email notifications for data task events are enabled.
If necessary, check the space-level and individual task notification settings, as these can override the default notification preferences.
Trigger an appropriate task event and verify that the directly assigned users receive the expected email notifications.
- Users can retain their existing group membership. Direct space membership is needed for notification eligibility.
- Confirm that an email provider is configured for the Qlik Cloud tenant.
- Adding a distribution list or group instead of individual users does not resolve this limitation.
- This solution applies until Qlik introduces support for notifications to group-based space members.
Qlik Cloud does not support sending space-related notifications to users who access a space only through group membership.
Although group membership provides access to the space and its resources, it does not make individual group members eligible to receive notifications from that space.
Users must be added directly to the space to receive supported space and task notifications, subject to their notification preferences and permissions.
This behavior is documented in Qlik Cloud Managing space notifications.
SUPPORT-10855
Use trace logging when a Snowflake connection, timeout, or staged-file upload failure needs more detail than the task log provides. Enable it for a short reproduction, collect the files, then restore normal logging.
The instructions in this article apply to Snowflake ODBC 3.x, and the connection properties require Data Movement gateway 2024.5.54 or later. Snowflake ODBC 4.x uses a different logging configuration.
If no logs appear
Check the executing gateway, folder existence and write permissions, available disk space, and whether a new ODBC connection was opened. A connection test alone may not exercise the failing upload. This guide enables Snowflake driver logging; unixODBC driver manager tracing uses separate settings.
It is possible to export the list of tenatnt users to a .json file using the "user ls" command from the Qlik Command Line Interface (qlik-cli).
The scripts provided in this article are provided as they are and they are for guidance only.
As a tenant admin, download and configure the Qlik-cli
qlik user ls --limit 1000 > tenantusers.json[
{
"assignedGroups": [],
"assignedRoles": [
{
"id": "608050f7634644db3678b1a2",
"level": "user",
"name": "Developer",
"type": "default"
},
{
"id": "608050f7634644db3678b17f",
"level": "admin",
"name": "TenantAdmin",
"type": "default"
},
{
"id": "605a1c2151382ffc836af862",
"level": "user",
"name": "SharedSpaceCreator",
"type": "default"
},
{
"id": "605a1c2151382ffc836af866",
"level": "user",
"name": "ManagedSpaceCreator",
"type": "default"
},
{
"id": "605a1c2151382ffc836af86b",
"level": "user",
"name": "DataSpaceCreator",
"type": "default"
},
{
"id": "605a1c2151382ffc836af85d",
"level": "admin",
"name": "AnalyticsAdmin",
"type": "default"
},
{
"id": "605a1c2151382ffc836af85f",
"level": "admin",
"name": "DataAdmin",
"type": "default"
},
{
"id": "63580b8d5cf9728f19217be0",
"level": "user",
"name": "PrivateAnalyticsContentCreator",
"type": "default"
},
{
"id": "6356f0425cf9728f1962b942",
"level": "user",
"name": "DataServicesContributor",
"type": "default"
}
],
"created": "2020-05-18T09:38:29.214Z",
"createdAt": "2020-05-18T09:38:29.214Z",
"email": "martina.testoni@dkdaklaldkdaklladaaddddl.com",
"id": "USERID1",
"lastUpdated": "2023-04-04T07:32:00.756Z",
"lastUpdatedAt": "2023-04-04T07:32:00.756Z",
"name": "Martina Testoni",
"picture": "https://s.gravatar.com/avatar/gravatarimage=pg\u0026d=https%3A%2F%2Fcdn.auth0.com%2Favatars%2Fdp.png",
"preferredLocale": "",
"preferredZoneinfo": "Europe/Copenhagen",
"roles": [
"Developer",
"TenantAdmin",
"SharedSpaceCreator",
"ManagedSpaceCreator",
"DataSpaceCreator",
"AnalyticsAdmin",
"DataAdmin",
"PrivateAnalyticsContentCreator",
"DataServicesContributor"
],
"status": "active",
"subject": "auth0|SUBJECTID2",
"tenantId": "TENANTID"
},
{
"assignedGroups": [],
"assignedRoles": [
{
"id": "608050f7634644db3678b17f",
"level": "admin",
"name": "TenantAdmin",
"type": "default"
},
{
"id": "605a1c2151382ffc836af86b",
"level": "user",
"name": "DataSpaceCreator",
"type": "default"
},
{
"id": "608050f7634644db3678b1a2",
"level": "user",
"name": "Developer",
"type": "default"
},
{
"id": "605a1c2151382ffc836af866",
"level": "user",
"name": "ManagedSpaceCreator",
"type": "default"
},
{
"id": "63580b8d5cf9728f19217be0",
"level": "user",
"name": "PrivateAnalyticsContentCreator",
"type": "default"
},
{
"id": "605a1c2151382ffc836af862",
"level": "user",
"name": "SharedSpaceCreator",
"type": "default"
},
{
"id": "6356f0425cf9728f1962b95c",
"level": "user",
"name": "Steward",
"type": "default"
},
{
"id": "605a1c2151382ffc836af85d",
"level": "admin",
"name": "AnalyticsAdmin",
"type": "default"
},
{
"id": "62bb165356d1879582c1b468",
"level": "admin",
"name": "AuditAdmin",
"type": "default"
},
{
"id": "605a1c2151382ffc836af85f",
"level": "admin",
"name": "DataAdmin",
"type": "default"
}
],
"created": "2023-03-31T08:44:37.332Z",
"createdAt": "2023-03-31T08:44:37.332Z",
"email": "Gentile.Faccenda@dkdaklaldkdaklladaaddddl.com",
"id": "USERID2",
"lastUpdated": "2023-04-03T11:24:35.037Z",
"lastUpdatedAt": "2023-04-03T11:24:35.037Z",
"name": "Gentile Faccenda",
"picture": "https://s.gravatar.com/avatar/randomurl=https%3A%2F%2Fcdn.auth0.com%2Favatars%2Fdp.png",
"roles": [
"TenantAdmin",
"DataSpaceCreator",
"Developer",
"ManagedSpaceCreator",
"PrivateAnalyticsContentCreator",
"SharedSpaceCreator",
"Steward",
"AnalyticsAdmin",
"AuditAdmin",
"DataAdmin"
],
"status": "active",
"subject": "auth0|IDPSUBJECT2",
"tenantId": "TENANTID"
}
]
qlik user ls --limit 1000 | ConvertFrom-Json | ConvertTo-Csv > tenantusers.csv
This article describes how to configure PostgreSQL 17 as both the source and target endpoint of a Qlik Replicate May 2026 task that uses Full Load and Apply Changes (change data capture, CDC). It follows a tested Windows setup from start to finish, and links to the Qlik Replicate documentation for the endpoint requirements.
All configuration examples on third-party components (not Qlik Replicate) are provided as is and not covered by Qlik Support. Additional steps or customizations may be needed in your environment.
Content
The example uses PostgreSQL 17 on Windows, with Qlik Replicate installed on a separate Windows server. The source and target databases can reside on the same PostgreSQL server for testing. Production environments typically use separate servers.
Example values used in this article:
psql -h <postgres_host> -p 5432 -U postgres -d postgres -W
CREATE DATABASE source;
CREATE DATABASE target;
\l
The required postgresql.conf values (wal_level, max_replication_slots, max_wal_senders, and the optional wal_sender_timeout) and the test_decoding output plugin are listed in Prerequisites (PostgreSQL source). Use the following steps to check and apply them.
\c source
SHOW wal_level;
SHOW max_replication_slots;
SHOW max_wal_senders;
ALTER SYSTEM SET wal_level = 'logical';
net stop postgresql-17
net start postgresql-17
Note: Changes to wal_level take effect only after a PostgreSQL restart.
Qlik Replicate requires the superuser role for CDC, unless the account is set up as described in Using an account without the “superuser” role. This example uses a dedicated non-superuser account. For the full list of permissions, see Required permissions.
CREATE ROLE qlik_user WITH LOGIN REPLICATION;
\password qlik_user
GRANT CONNECT ON DATABASE source TO qlik_user;
ALTER DEFAULT PRIVILEGES FOR ROLE postgresDefault privileges apply only to objects created by the named role. If other roles create source tables, set their default privileges separately.
IN SCHEMA public
GRANT SELECT ON TABLES TO qlik_user;
GRANT CREATE ON SCHEMA public TO qlik_user;
Prerequisites (PostgreSQL source) describes the pg_hba.conf entry that the Qlik Replicate server requires, including the replication keyword. Use the following steps to verify the active configuration.
SHOW hba_file;
SELECT line_number, type, database, user_name,A value in the error column indicates a rule that PostgreSQL could not load.
address, auth_method, error
FROM pg_hba_file_rules
ORDER BY line_number;
host source qlik_user <replicate_server_ip>/32 scram-sha-256Use the authentication method and network restrictions appropriate for your environment.
SHOW listen_addresses;
SHOW port;
Note: Changes to pg_hba.conf require a configuration reload. Changes to listen_addresses require a PostgreSQL restart.
A non-superuser account requires the attrep_ddl_audit table, the attrep_intercept_ddl() function, and the attrep_intercept_ddl event trigger. Create these objects, and grant the account access to the audit table and its sequence, exactly as described in Using an account without the “superuser” role. The event trigger must be created with a superuser account.
If the objects are not in the public schema, enter their schema in the Create DDL artifacts in schema field on the source endpoint’s Advanced tab. See Setting advanced connection properties (PostgreSQL source).
After completing the documented procedure, verify the event trigger:
SELECT evtname, evtevent, evtenabled
FROM pg_event_trigger
WHERE evtname = 'attrep_intercept_ddl';
An enabled trigger returns:
attrep_intercept_ddl | ddl_command_end | O
Note: Do not grant permanent superuser privileges to the replication account only to bypass the DDL setup.
where psqlExample output:
psql --version
C:\Program Files\PostgreSQL\17\bin\psql.exe
psql (PostgreSQL) 17.11
The target account requirements are listed in Security requirements (PostgreSQL target). The grants below were used in this tested example, where Qlik Replicate creates and maintains the tables in the public schema of an existing target database.
GRANT CONNECT ON DATABASE target TO qlik_user;
\c target
GRANT USAGE, CREATE ON SCHEMA public TO qlik_user;
The exact privileges depend on the task settings, schema ownership, and selected target operations.
A successful test confirms connectivity only. The task also requires the CDC prerequisites above to start successfully.
Monitor the Full Load progress and the SOURCE_CAPTURE, TARGET_LOAD, and TARGET_APPLY log messages.
Note: Use Fresh Start only for a new test task, or where resetting the existing replication state is acceptable.
psql -h <target_host> -p 5432 -U postgres -d target -W
\dt public.*
SELECT COUNT(*) FROM public.customers;
SELECT COUNT(*) FROM public.orders;
SELECT COUNT(*) FROM public.products;
The Apply Exceptions table (attrep_apply_exceptions) is always created. The other control tables depend on the task’s Control tables settings.
\dt public.attrep_*
SELECT 'attrep_status' AS table_name, COUNT(*) AS row_count
FROM public.attrep_status
UNION ALL
SELECT 'attrep_history', COUNT(*)
FROM public.attrep_history
UNION ALL
SELECT 'attrep_ddl_history', COUNT(*)
FROM public.attrep_ddl_history
UNION ALL
SELECT 'attrep_apply_exceptions', COUNT(*)
FROM public.attrep_apply_exceptions
UNION ALL
SELECT 'attrep_suspended_tables', COUNT(*)
FROM public.attrep_suspended_tables;
Some control tables remain empty until the corresponding task event occurs.
After Full Load completes and the task enters change processing:
INSERT INTO public.customers
(customer_id, customer_name, email, city)
VALUES
(9001, 'CDC Test', 'cdc@example.com', 'Denver');
UPDATE public.customers
SET city = 'Boston'
WHERE customer_id = 9001;
DELETE FROM public.customers
WHERE customer_id = 9001;
This article describes how to manually move the Qlik Sense Repository Database from the PostgreSQL 14.x instance bundled with Qlik Sense Enterprise on Windows to a separately installed (unbundled) PostgreSQL 18 instance.
The procedure backs up the bundled instance, restores it into the new instance, and then removes the bundled database service.
This is the manual method otherwise executed by the Qlik PostgreSQL Installer. QPI currently does not support PostgreSQL 18.
Content
Environment
Perform a full backup of the Qlik Sense site, including the Qlik Sense Repository Database, the Qlik Sense share folder, and the Qlik Sense CA-signed certificates. See How To Take Backup And Restore Qlik Sense Enterprise on Windows.
Create an easily accessible backup folder. Example: C:\backup.
SET PGPASSWORD=your_postgres_password
cd "C:\Program Files\Qlik\Sense\Repository\PostgreSQL\14\bin"
pg_dumpall.exe -h localhost -U postgres -p 4432 -f c:\backup\backup_db.sql
If you are prompted for a password:
cd "C:\Program Files\PostgreSQL\18\bin"
psql -h localhost -U postgres -p 5432 -f c:\backup\backup_db.sql
If you get "password authentication failed for user postgres":
Either copy the following two files from the old data folder into the new one:
Or verify and modify both files manually:
host all all 0.0.0.0/0 md5
With pgAdmin or DBeaver, check that all of the following databases are present:
If any databases are missing, restore the dump once again, this time using port 4432:
psql -h localhost -U postgres -p 4432 -f c:\backup\backup_db.sql
After a successful restore, delete the PGPASSWORD environment variable.
SET PGPASSWORD=
Before you can begin testing, remove the Qlik Sense Repository Database dependency from the Qlik Sense Repository Service:
sc config QlikSenseRepositoryDatabase depend= /
sc config QlikSenseRepositoryService depend= /
After the dependency is removed:
Failing to remove the old service leads to upgrade or patching issues.
This is optional if you upgrade Qlik Sense immediately after unbundling the PostgreSQL database, since a Qlik Sense upgrade installs the correct binaries. But if you do not upgrade right away, reinstall the binaries immediately. Failing to do so will lead to service configuration script errors.
cd C:\ProgramData\Package Cache\{GUID}
msiexec.exe /qb /i "PostgreSQL18.msi" SKIPINSTALLDBSERVICE="1" INSTALLDIR="C:\Program Files\Qlik\Sense"
msiexec.exe /qb /i "PostgreSQL14.msi" SKIPINSTALLDBSERVICE="1" INSTALLDIR="C:\Program Files\Qlik\Sense"
Qlik Cloud tenants are the highest level of logical isolation provided to our customers. The subscriptions and associated entitlements (also known as licenses) that customers purchase from Qlik are not fixed to these tenants. When needed, a customer can update the entitlement used by their tenant. This article covers how to do this, as well as all considerations before moving.
You should not attempt to update your tenant entitlement unless directed to do so by Qlik, or you are an OEM customer who is managing multiple entitlements for their estate.
The steps in this article only apply to User-Based Subscriptions. To convert your tenant from an evaluation tenant to a paid tenant, or to convert from a user-based subscription to a capacity-based subscription, contact Qlik Support.
Content:
There are three scenarios where you might need to update your entitlement:
If you are an OEM or Enterprise customer leveraging multiple tenants in Qlik Cloud, please also consider reviewing the Platform Operations series on qlik.dev to learn more about managing these estates prior to changing your entitlements.
Before you begin migrating your subscription or entitlement, consider:
Updating the entitlement requires four steps:
Your SLK is available through:
When you migrate between entitlements, any user assignments will be reset. You will need to export any current assignments if you wish to reassign them.
There are three ways of doing this:
If you have many users, both option a and b will require you to paginate to get all results.
Results will look like:
If required, reassign entitlements which were exported in step 2. You can do this in two ways:
curl -L -X POST 'https://<hostname>.<region>.qlikcloud.com/api/v1/licenses/assignments/actions/add' \
-H 'Authorization: Bearer ey...' \
-H 'Content-type: application/json' \
-H 'Accept: application/json' \
--data-raw '{
"add": [
{
"subject": "1ef2caed0dbe0a66a24ccadf61546099",
"type": "professional"
}
]
}'
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.
Qlik Cloud Tenant Admins report that the IP Allowlist option is missing from Administration > Settings. In some cases, the Alerts submenu is also unavailable (existing alerts may still be visible, but create or edit is not possible).
The Feature Preview settings may also appear under an “Other” tab instead of their normal location. The issue affects multiple Tenant Admins in the same tenant and appears suddenly without any configuration changes in Qlik Cloud.
The missing menu options are caused by blocked outbound network calls to Qlik Cloud feature-flag and analytics services. When these calls fail, the user interface hides the related features.
This issue is almost always network-related (proxy / SSL interception / DLP) and not a change in Qlik Cloud itself. Testing from a different network (e.g. mobile hotspot or unrestricted network) can quickly confirm the diagnosis.
Qlik Cloud uses LaunchDarkly for feature flags and Pendo for in-product guidance and analytics. Several Administration features (including IP Allowlist and Alerts) depend on successful calls to these services.
When a corporate proxy, SSL inspection appliance, or Data Loss Prevention tool blocks or intercepts traffic to domains such as clientsdk.launchdarkly.com or Pendo endpoints, the browser receives no response (or a CORS/connection error). The Qlik Cloud frontend then falls back to a reduced feature set and hides the corresponding menu options.
This explains why the same tenant can show the full Administration menu from an unrestricted network while the options are missing when accessed from the corporate network.
A Talend Remote Engine running as a service on Linux repeatedly shows Unavailable in TMC during a consistent daily window (for example, 05:00 to 06:30 CST). The service appears healthy on the host, and no network issues are found. Scheduled tasks on the engine may fail or be skipped during this window.
Typical log indicators:
The most likely cause is JVM unresponsiveness under peak concurrent load. Many parallel jobs and large file transfers (around 100 MB archives) were scheduled in the same window. This can cause host resource contention (memory or swap pressure, prolonged garbage collection, or disk/network-mount I/O stalls). The wrapper then killed and restarted the engine JVM. While the engine reconnects, TMC marks it as Unavailable, even though the service eventually recovers by itself.
In earlier versions of the cFile before Talend Studio version 2026-01, the success field was intentionally left blank to keep the file in its original location. After the migration, even if the success field is left intentionally blank, the component will create a ".camel" folder and move the successfully consumed file there.
Caused by QAPPINT-3213.
QAPPINT-3213 is expected to be resolved in the Talend Studio R2026-11 release. Review the relevant release notes for details.
No workaround is available.
QAPPINT-3213 Cfile 2026-01 changes is forcing a file move when NOOP is disabled when it is successfully consumed
QAPPINT-3213
The Scheduled Job icon in the Job Conductor section continues to display even after the job has completed.
This behavior started after patching the Talend Administration Center to 2026-09.
Before patching, the Scheduled Job icon would disappear once the job was completed, and only the corresponding Job Completed or Job Failed icon would be displayed.
This is caused by QTAC-3083.
QTAC-3083 is expected to be resolved in the November Talend Administration Center patch. Review the relevant release notes for details.
No workaround is available.
QTAC-3083 Timeline: scheduled events not removed after the scheduled run (regression from Quartz 2.5.x upgrade)
QTAC-3083
A Qlik Replicate task using an Amazon RDS for PostgreSQL source, with the supportCdcPartitionedTables internal parameter enabled, terminates with a broken connection. The SOURCE_CAPTURE log component reports:
Failed to get partition details about table <schema>.<tablename>
Failed to get parent table details of child table '<schema>.<tablename>'
The error can reference tables that are not included in the task. The task restarts automatically and resumes processing.
The partition error is a side effect, not a partitioning metadata failure. The SOURCE_CAPTURE log also records the underlying error, showing that the database connection was dropped:
RetCode: SQL_ERROR SqlState: HY000 NativeError: 1 Message: FATAL: terminating connection due to idle-session timeout SSL connection has been closed unexpectedly
The error can appear in every environment that shares the same source endpoint configuration.
For more information about Internal Parameters, see Qlik Replicate: How to set Internal Parameters and what are they for?.
On the Qlik Replicate server, set the operating system’s TCP keepalive interval to match, or be shorter than, the idle-session timeout enforced by the Amazon RDS for PostgreSQL instance or any intermediate firewall.
An idle-session timeout terminates the connection between Qlik Replicate and the Amazon RDS for PostgreSQL instance. The timeout can be enforced at the database level or by a network component, such as a firewall. The query that is running when the connection drops, in this case a partition-tree lookup, fails with an SSL connection error.
SUPPORT-11452
With a Microsoft SQL Server source, Qlik Replicate tasks can miss transactions in one of two ways:
In both cases, rows committed on the source are missing from the target, and the affected tables must be fully reloaded.
For more information about Internal Parameters, see Qlik Replicate: How to set Internal Parameters and what are they for?.
If transactions in the SQL Server transaction log are not captured while the task runs without a restart, contact Qlik Support.
Starting a task by timestamp is not exact. The LSN that Qlik Replicate derives from the requested timestamp can be later than expected, so the task resumes after transactions that were committed around the restart point.
SUPPORT-11536
When the issue is related to the web browser cache and the user does not want to clear all browser cache, then what is the right approach to delete the cache only for the specific site?
To delete cookies and cache for a specific site in Google Chrome, follow the instructions given below:
To expedite the investigation for Qlik Data Gateway - Direct Access cases, the following information is required.
Without this information, Qlik Support cannot begin reviewing the issue.
C:\Program Files\Qlik\ConnectorAgent\data\logs
C:\ProgramData\Qlik\Gateway