Loop and Reduce will remove an app's section access that was defined through the load script. Offline usage needs to be enabled in your tenant's management console in order to use the Loop And Reduce block on an app outside a personal space. More information on offline usage.

See How to Loop and Reduce with always one selected value fields if your app contains always one selected value fields.

This article explains how a loop and reduce operation can be performed on a Qlik Sense app by using Qlik Application Automation. It covers two examples, in the first one, the reloaded apps will be (re)published to one space. In the second example, each reduced app will be (re)published to a separate space.

This article covers two advanced examples, a more basic example can be found here .

Covered in this article:

• 1. Loop and reduce to one space
• 2. Loop and reduce to multiple spaces

The source app used in this article can be downloaded here.

Attached to this article are 2 files of the exported automations used in this article. More information on importing automations can be found here.

1. Loop and reduce to one space

In this example, all reduced apps will be (re)published to the same space.

Create a new automation and follow these steps to perform a loop and reduce action on a Qlik Cloud app:

1. Go to the Qlik Cloud Services connector and search for the block "Loop And Reduce". Drag this block inside the automation editor.
   
   
2. Specify the id for the app that should be used as a source app. The reduction will be performed on this app. Next, specify the field name over which the loop should run, for each unique value of the specified field name, a reduced app will be created. In this example, CountryName will be used as the reduction value.
   
   
   

    

3. The reduced apps are stored on the Temporary File services. The Loop And Reduce block will return a list of file ids together with the unique value of the reduction field and a list of sheet ids for the sheets that were public on the source app.
   
   
4. The next step is to import the apps from the Temporary File services. To do this search for the block "Import App From Export Id" and drag this block in the loop that's created by the Loop And Reduce block. This block will import one app from the temporary file services into your personal space.
   
   Tip: Specify the reduced value that will be returned by the Loop and Reduce block in the Name parameter of the Import block.
   
   See (Import App From Export) for an example:
   
   

   

5. When an app is imported, all sheets will be made private, this is the default behavior of the import app block. The next step is to publish the sheets that were public in the source app.
   
   
6. Because each reduced app will have a list of sheets that are public, a Loop block is necessary to loop over the list. Search for a "Loop" block in the block menu or find it under Basic and connect it right below the "Import App From Export Id" block. Specify the "Public Sheets" list returned by the Loop And Reduce block as the value for the "Loop over items of list" input parameter of the Loop block.
   
   

   

7. Now, to publish each sheet of the imported app, search for the block Publish Sheet in the Qlik Cloud Services connector and drag that block in the loop generated by the Loop block. In this block, specify the id returned by the Import App block as App Id and use the current item in the loop as Sheet Id.
   
   

   

8. The next step is to publish or republish the imported app to a managed space. This can be done with the Publish App To Managed Space block. Search for this block in the Qlik Cloud Services connector and connect it below the loop block. Set the Run Mode to "(Re)publish by name", if the managed space already contains an app with the same name as the imported app, the imported app will be republished, or else it will be published.
   
   
9. In the configuration of the Publish App To Managed Space block, set the App Id equal to the id returned by the Import App From Export Id block. For the Space Id, perform a lookup or manually enter an id, make sure you're specifying a managed space. The Data parameter should be set to "source".
   
   

   

10. Finally, when your app is published to a managed space, the imported app will still exist in your personal space. To remove this app, search for the block "Delete App" in the Qlik Cloud Services connector and connect it to the Publish App To Managed Space block. Specify the id returned by Import App From Export Id as the App Id in the block's settings.
    
    

An example of a completed automation:

Attached example file: loop_and_reduce_to_same_space.json

2. Loop and reduce to multiple spaces

In this example, each reduced app will be published to a different space. We'll use the Insurance Claims app and the automation for the first example again. Since this app reduces on the field CountryName, we'll start by creating a managed space for each unique value that's found for CountryName. 

Next is to create a mapping for each unique reduction value and the corresponding space's id. There are multiple ways to achieve this. In this example, this mapping is stored in a JSON list of objects with the keys reduction_value and space_id. Feel free to use an automation to create the managed spaces and build this list.

Example:

[
	{
		"reduction_value": "Scotland",
		"space_id": "6138a3062c1054d8158c189a"
	},
	{
		"reduction_value": "Northern Ireland",
		"space_id": "6138a318faed485d36ae911f"
	},
	{
		"reduction_value": "England",
		"space_id": "6138a337faed485d36ae9126"
	},
	{
		"reduction_value": "Wales",
		"space_id": "6138a33f98b0d0bf7e719dfb"
	},
	{
		"reduction_value": "Guernsey",
		"space_id": "6138a349faed485d36ae912b"
	},
	{
		"reduction_value": "Isle of Man",
		"space_id": "6138a35aba392246d331e611"
	},
	{
		"reduction_value": "Jersey",
		"space_id": "6138a3653ec592fe53a8d55b"
	}
]

The next step is to store the mapping in the automation. Execute the following steps to do this:

1. Search for the Variable block and add this to the automation.
   
   
2. Go to the block's settings, click Manage variables and add a new variable of type list.
   
   
3. Go to the operations section of the variable and set the first operation to empty the variable.
   
   
4. Add a second operation Merge other list into... and click the List input field of that operation, in the dropdown that appears, select Add Formula.
   
   
5. From the formula picker, search for the formula Object and select it. Copy the JSON mapping to the json input field of the Object formula and click Save.
   
   
6. Add the block to the beginning of the automation from the first part of this article:
   
   

   

7. The next step is to find the right space id for each reduced app. To do that, add the block Lookup Item In List in the automation right before the block Publish App To Managed Space.
   
   
8. Go to the settings of the Lookup Item In List block and specify the variable that contains space_id/reduction_value mapping as input list. The condition inside the lookup should compare the mapping's reduction_value to the Reduced Value of the current item in the loop of Loop And Reduce. See the below image for an example:
   
   

   

9. Finally, specify the space_id from the output of the lookup block as Space Id in the settings of the Publish App To Managed Space.
   
   
   

    

Attached example file: loop_and_reduce_to_mulitple_spaces.json

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.

There is currently no native option in a Qlik Talend Cloud tenant to duplicate a connection. To create multiple connections from the same source, users must manually create a new connection and re-enter credentials each time.

The following two options exist:

• The REST API duplicate connection endpoint
• A Qlik Automate automation

This article covers two automations that can be customized to fit your needs. While the automations are not a true duplicate feature, they do automate the creation using existing connection details.

The information in this article is provided as-is and will be used at your discretion. For more direct assistance, post your query in the Qlik Automate forums or engage Qlik Professional Services. 

Requirements

• Appropriate permissions to create and run Qlik Automate automations
• The JSON file template, downloaded from this article
• Initial (base) connection needs to be manually created in the UI

Setup Instructions

1. In your tenant, navigate to Automations 
2. Click Create new automation and select the Blank automation card
3. Name your automation, choose a space, and click Create 
4. Click Create new automation and select a Blank automation from the available templates
5. Right-click anywhere in the open space, select Upload workspace, and choose the downloaded JSON file; see Qlik Automate: How to import and export automations for details

Running the Automation

Once the workspace is uploaded, the automation and all its blocks will be displayed. Before you can run it, you need to select the data space where your connection exists. The new connections will be created in the same space.

1. Click on the Get Space block
2. In the Space Id field, select do lookup and find your space
   
   
   
   
3. Run the automation

How it works

Count-Based Duplication Automation

Inputs:

• Original Connection Name
• New Base Connection Name
• Count (number of duplicates to create)

Behavior:

Creates multiple connections using incremental numbering

Example:

• Original: Workday
• New Name: Workday_new
• Count: 2

Result:

• Workday_new_1
• Workday_new_2

Suffix-Based Duplication Automation

Inputs:

• Original Connection Name
• New Base Connection Name
• Suffix list (comma-separated)

Behavior:

Creates connections using custom suffixes for naming flexibility

Example:

• Original: Workday
• New Name: Workday_new
• Suffixes: abc,def,hij

Result:

• Workday_new_abc
• Workday_new_def
• Workday_new_hij

Environment

• Qlik Talend Cloud
• Qlik Automate

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-11415.

• 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-11415

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-11415 for reference.

Environment

• Qlik Replicate

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.

Requirements

The user running the automation needs to have:

• API permission; see Permission settings — Features and actions | help.qlik.com.
• The audit admin role; see Permissions granted by security roles | help.qlik.com.

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. 

This article is currently under review.

This article explains how to extract changes from a Change Store and store them in a QVD by using a load script in Qlik Analytics. 

The article also includes

• An app example with an incremental load script that will store new changes in a QVD
• Configuration instructions for the examples

Scenario

This example will create an analytics app for Vendor Reviews. The idea is that you, as a company, are working with multiple vendors. Once a quarter, you want to review these vendors.

The example is simplified, but it can be extended with additional data for real-world examples or for other “review” use cases like employee reviews, budget reviews, and so on.

The data model

The app’s data model is a single table “Vendors” that contains a Vendor ID, Vendor Name, and City:

Vendors:
Load * inline [
"Vendor ID","Vendor Name","City"
1,Dunder Mifflin,Ghent
2,Nuka Cola,Leuven
3,Octan, Brussels
4,Kitchen Table International,Antwerp
];

The Write Table

The Write Table contains two data model fields: Vendor ID and Vendor Name. They are both configured as primary keys to demonstrate how this can work for composite keys.

The Write Table is then extended with three editable columns:

• Quarter (Single select)
• Action required? (Single select)
• Comment (Manual user input)

Prerequisites

• A shared space
• A managed space (optional but advised for the tutorial)
• A connection to the Change-stores API to the Analytics REST connector in the shared space. A step-by-step guide on creating this connection is available in Extracting write table changes with the REST connector in Qlik Cloud.

Steps

1. Upload the attached .QVF file to a shared space
2. Open the private sheet Vendor Reviews
3. Click the Reload App (A) button and make sure data appears (B) in the top table
   

   
   

4. Go to Edit sheet (A) mode
5. Drag a Write Table Chart (B) on the top table, and choose the option Convert to: Write Table (C).
   
   This transforms the table into a Write Table with two data model columns Vendor ID and Vendor Name.
   
   
   

    

6. Go to the Data section in the Write Table’s Properties menu and add an editable column
   
   
   

    

7. This prompts you to define a primary key inside the table. Click Define (A) in the table and use both Vendor ID and Vendor Name as primary keys (B).
   
   You can also just use Vendor ID, but we want to show that this also supports composite primary keys.
   
   
   
   
   
   
8. Configure the editable column:
   
   
   • Title: Quarter
   • Show content: Single selection
   • Add options for Q1Y26 through Q4Y26.
     
     Tip! Also add an empty option by clicking the Add button without specifying a value.
     
     
     

      

9. Add another Editable column with the below configuration
   
   
   • Title: Action required
   • Type: Single select
   • Options:  Yes and No
     
     

     

10. Add another Editable column with the below configuration
    
    
    • Title: Review
    • Type: Single select
    • Options:  Yes and No
      
      
      
      
11. The Write Table is now set up.
    
    Go to the Write Table’s properties and locate the Change store (A) section. Copy the Change store ID (B).
    
    
    

     

12. Leave the Edit sheet mode. Then add changes for at least two records. Save those changes.
    
    
    

     

13. Go to the app’s load script editor and uncomment the second script section by first selecting all lines in the script section (CTRL+A or CMD+A) (A) and then clicking the comment button (B) in the toolbar.
    
    
    

     

14. Configure the settings in the CONFIGURATION part at the end of the load script
    
    
    

     

15. Update the load script with the IDs of the editable columns.
    
    The easiest solution to get these IDs is to test your connection. Make sure the connection URL is configured to use the /changes/tabular-views endpoint and uses the correct change store ID.
    
    
    

     

16. Copy and paste the example load script (for the editable columns only) and paste it in the app’s load script SQL Select statement that starts on line 159:
    
    
    

     

17. Replace the corresponding * symbols in the LOAD statement that starts on line 176:
    
    
    

     

18. Choose which records you want to track in your table by configuring the Exists Key on line 216.
    
    This key will be used to filter the “granularity” on which we want to store changes in the QVD and data model, as the load script will only load unique existing keys (line 235).
    
    
    • $(vExistsKeyFormula) is a pipe-separated list of the primary keys.
    • In this example, Quarter is added as an additional part of the exists key to keep track of changes by Quarter.
    • Optionally, this can be extended with createdBy and updatedAt to extend the granularity to every change made:
      
      
      

       

19. Reload the app and verify that the correct change store table is created in your data model. The second table in the sheet should also successfully show vendors and their reviews.

Environment

• Qlik Cloud Analytics

Installing the QlikView Plugin with the executable file and parameters /S /v /qn doesn't work.
The system is installing but after the installation the software isn't available on the target system.

Environment:

• QlikView Desktop, all versions
• QlikView IE Plugin, all versions

Resolution:

Note1: The same procedure below can be done for QlikView Desktop .exe file
Note2: Newer versions of QlikView installation includes a 64-bit version of the QV IE Plugin, by default.

1. First you'll need to extract the msi file from the exe file. 

2. Start the installation file. The QlikView installation will come op with the following dialog: 

3. Do not close the dialogue box. Now you have to move to the user temp folder to pick up the .msi file. 

QVPlugin:

QlikView:

4. Copy the .msi file to your target location. (e.g C:\)
5. Now you can close the dialog box.
6. Once the .msi file has been extracted. Press Start -> Run and enter the following command:

msiexec /i "C:\QVPluginSetup.msi" ALLUSERS=1 /quiet

 7. Another example with the QlikView msi:

qlikviewx64.msi REINSTALL=ALL REINSTALLMODE=vomus

SAP’s recent updates related to ODP-RFC data extraction have raised questions among customers using SAP connectivity with Qlik products, including Talend Studio. For details on the announcement, see Important update on SAP Data Access Restrictions and your Qlik Integration | Qlik Support.

This article clarifies the current understanding of the impact on Talend Studio specifically, and helps customers identify whether their Talend Studio jobs are affected.

Scope of the SAP Change

The SAP changes described in SAP Note 3255746 and related API policy updates are specifically related to the use of the ODP-RFC extraction interface for SAP systems.

This does not represent a general restriction on SAP connectivity or SAP integrations with Qlik products.

Based on Qlik’s current understanding, the impact is specific to ODP-RFC-based extraction patterns. Customers using SAP integrations that do not rely on ODP-RFC are not currently directly impacted by this SAP update, subject to their SAP configuration, licensing terms, APIs used, and SAP entitlement.

Impact on Talend Studio

For Talend Studio, the component currently identified as impacted is:

The key point is that the impact is determined by the extraction mechanism being used, not simply by the fact that a customer is connecting Talend Studio to SAP.

Current Understanding of the SAP Integration Mechanism 

For CDS Views, the important distinction is the access path. A CDS View is not, by itself, the determining factor. If the CDS View is extracted through ODP-RFC, it should be considered within the impacted scope. If it is accessed through another mechanism, such as OData, and does not rely on ODP-RFC, it is not currently directly impacted by this SAP update.

Similarly, SAP JCo is a technical library provided by SAP. The use of JCo alone is not the determining factor. The relevant question is whether the integration relies on ODP-RFC.

Talend Studio SAP Components: Direct Impact by Access Mechanism

The impact of the SAP ODP-RFC restriction depends on the access mechanism used by the Talend Studio component. The following components are not directly impacted by this restriction, provided they are not used as part of an ODP-RFC-based extraction pattern. For tSAPADSOInput, the impact depends on the selected configuration:

Recommended Path for ODP Customers

For customers currently using ODP-based extraction, SAP’s recommended alternative is OData.

In Talend Studio, SAP OData integration is supported through the following components:

For extraction scenarios, customers currently using tSAPODPInput should evaluate whether the required SAP business objects, CDS Views, or services can be exposed and consumed through OData using tSAPODataInput.

For write-back or update scenarios through OData, Talend Studio also provides tSAPODataOutput.

Some SAP-side configuration may be required, depending on the SAP system, the business objects involved, and how the relevant services are exposed.

What Customers Should Do

Customers using Talend Studio with SAP should:

• Identify whether their current Talend Studio jobs use tSAPODPInput or another ODP-RFC-based extraction mechanism.
• If ODP-RFC is being used, engage with Qlik to evaluate alternative integration paths, including OData with tSAPODataInput.
• If non-ODP SAP components are being used, no immediate technical action is currently expected based on Qlik’s present understanding.
• Review SAP licensing, entitlement, API usage rights, and SAP configuration directly with SAP.

Key Takeaways

The SAP ODP-RFC change is important, and customers using ODP-based extraction should assess their exposure.

However, this should not be interpreted as a broad restriction on Talend Studio SAP connectivity. Based on Qlik’s current understanding, the identified impact for Talend Studio is limited to scenarios that rely on the SAP ODP API through the RFC protocol, including tSAPODPInput and the RFC/ODP API-based configuration of tSAPADSOInput.

Talend Studio continues to provide several SAP connectivity options that do not rely on ODP-RFC. For customers currently using ODP-based extraction, OData should be evaluated as the recommended alternative path, especially through tSAPODataInput for extraction scenarios.

This guidance reflects Qlik’s current understanding of SAP’s restrictions, which are outside Qlik’s control and may evolve as SAP provides further clarification. This article should not be interpreted as legal or licensing advice.

Customers should consult SAP’s official communications and validate their SAP licensing position, entitlement, API usage rights, and operational impact directly with SAP.

Roadmap statements, if any, are forward-looking and do not represent commitments.

Environment

• Talend Studio

Launching the Hub produces the error

The Qlik Sense Management Console is reachable and it displays no Engine errors. The Qlik Sense Engine is up and running. 

This happens on a Central node, and there is no issue with port 4900 (as detailed in article Proxy RIM node error from HUB "the proxy is waiting for a new session).

If you have just patched to a more recent version of Qlik Sense, then you may also need to try Recreating the Qlik Sense Root Certificate (Root CA) as NodeJS has newer requirements for the certificate.

Environment: 

Resolution:

• Restart the Qlik Sense Dispatcher Service
• If the issue persists, restart the server hosting Qlik Sense
• Verify that the C:\ drive of the Qlik Sense server host has not reached critical disk space capacity issues
• Certificates may need to be recreated. See How to recreate or just delete certificates in Qlik Sense - No access to QMC or Hub for details. 

Related content:

Proxy RIM node error from HUB "the proxy is waiting for a new session"

Should the issue persist, please contact Qlik Support at support.qlik.com.

Executing tasks or modifying tasks (changing owner, renaming an app) in the Qlik Sense Management Console and refreshing the page does not update the correct task status. Issue affects Content Admin and Deployment Admin roles.

The behaviour began after an upgrade of Qlik Sense Enterprise on Windows. 

Fix version:

This issue can be mitigated beginning with August 2021 by enabling the QMCCachingSupport Security Rule.

Solution for August 2023 and above:

Enable QmcTaskTableCacheDisabled.

To do so:

1. Navigate to C:\Program Files\Qlik\Sense\CapabilityService\
2. Locate and open the capabilities.json
3. Modify or add the QmcTaskTableCacheDisabled flag for these values to true
   
   {"contentHash":"CONTENTHASHHERE","originalClassName":"FeatureToggle","flag":"QmcTaskTableCacheDisabled","enabled":true}
   
   Where CONTENTHASHHERE matches the number in all other features listed in the capabilities.json.
   
   Example:
   
   
   
   This will disable the caching on the tasks table only, leaving the overall QMC Cache intact to gain performance. If you had previously set QmcCacheEnabled, QmcDirtyChecking, QmcExtendedCaching to false, please set it to true again.
   
   
4. Restart the Qlik Sense services

Workaround for earlier versions:

Upgrade to the latest Service Release and disable the caching functionality: 

To do so:

1. Navigate to C:\Program Files\Qlik\Sense\CapabilityService\
2. Locate and open the capabilities.json
3. Modify the flag for these values to false
   • QmcCacheEnabled
   • QmcDirtyChecking
   • QmcExtendedCaching
4. Restart the Qlik Sense services
   
   

NOTE: Make sure to use lower case when setting values to true or false as capabilities.json file is case sensitive.

Should the issue persist after applying the workaround/fix, contact Qlik Support.

Internal Investigation ID(s): 

QB-2096
QB-5168
QB-7655
QB-17238

Environment

Qlik Sense Enterprise on Windows 

Qlik is removing legacy attributes from webhook payloads on October 6^th, 2026. Unless updated to use the new attributes, this change will break webhook-triggered automations that rely on the removed fields.

During the transition, some events include both legacy and CloudEvent fields, but this is temporary. Once CloudEvent-only enforcement begins, automations that still rely on legacy fields can fail.

This guide explains how to identify affected automations, update them, validate them, and return them safely to production.

Events affected by this migration

The following legacy webhook events are being updated to the CloudEvent format. Any events not listed here already adhere to the CloudEvent format and are not affected.

Both App Reload Finished and Reload Finished are available. During migration, evaluate Reload Finished as the preferred target event where it supports your workflow requirements.

Changes in the event payload

The data delivered by these events remains the same, but the field names, casing, and structure of the payload are changing. During the transition, each event includes both legacy and CloudEvent fields simultaneously, so your automations can use either. After enforcement, only CloudEvent fields will be present.

The following field-level changes apply across all impacted events:

If your automation references any field in the left column, it needs updating.

Changes in the editor experience

In the automation editor, automations that still use legacy event definitions will be flagged for migration. A banner appears in the editor, and the affected event type shows a deprecated indicator in the event selector.

When you update the trigger to a CloudEvent-compatible event, the editor shows which blocks directly reference payload fields that have changed or moved. This impact notification is your starting point for the block-level migration in Step 5 below.

If your automation currently uses App Reload Finished, consider selecting Reload Finished during migration where it fits your use case. Reload Finished is the recommended option for future use.

Webhook configuration for automations needs to be migrated from within the automation workflow rather than directly from the webhooks admin screen.

Who does what

Tenant admins coordinate migration at the tenant level. They identify which webhooks still use legacy event behaviour, locate impacted automations and owners, and drive progress tracking. Tenant admins can see which automations are affected by the webhook admin console, but changes to automation logic require the automation owner.

Automation owners perform the actual migration work in the editor. They update trigger events, correct broken field references, test end-to-end behaviour, and republish.

Recommended migration process

Step 1: Build your migration inventory (Tenant admin)

Open the webhook admin console and identify webhooks still tied to legacy event usage. For each one, note the associated automation, the owner, and the space it belongs to. This is your migration inventory. Prioritise critical workflows, especially those tied to production processes, first.

Step 2: Notify automation owners

Contact each automation owner with the list of impacted automations and a clear target completion date. Share this guide as a reference for migration steps. Treat migration as a coordinated reliability initiative so owners have time to test properly rather than rushing at the enforcement deadline.

Step 3: Confirm migration indicators in the editor (Automation owner)

Open the automation in the editor and confirm the migration banner is shown, and the trigger event carries the deprecated label. This confirms that the automation is in scope and needs updating. If you want to test your changes, consider duplicating the automation.

Step 4: Update the trigger event

In the webhook trigger block, open the event selector and choose the matching CloudEvent-compatible event.

If the current trigger is App Reload Finished, consider selecting Reload Finished where appropriate.

After saving the trigger, review the impact notification listing blocks referencing legacy payload fields. This list is the scope of your block-level work. 

Once you've made all changes and saved the automation, the webhook associated with the automation will start emitting CloudEvent-only fields.

Step 5: Update all impacted blocks

Work through each impacted block listed in the impact notification. Replace legacy field references with their CloudEvent equivalents using the field mapping table above. Check conditions, mappings, expressions, templates, and outbound payloads. Field names are now lowercase, and some have moved from the extensions object to the root or into the data object, so do not assume old paths are still valid. Refer to the legacy field table above.

This is especially important when moving from App Reload Finished to Reload Finished, because payload details can differ, and field references may require additional remapping.

Step 6: Test the automation

Run the automation with representative data and confirm that trigger behavior, field mappings, branch conditions, integrations, and error handling all work as expected. Before you begin, consider whether this automation performs transactional actions (such as orders, payments, or similar). If it does, coordinate with stakeholders on safe test data and timing. If possible, test during a maintenance window or use synthetic data that mimics the payload structure without triggering unwanted side effects. Compare the outputs against your expected business behavior.

Step 7: Save, enable, and monitor

Enable the automation according to your normal release process. Monitor early production runs for regressions and record migration completion status in your tenant tracking. Report completion to the tenant admin so they can update the migration inventory.

What to watch for during migration

Most migration defects appear in blocks that directly consume trigger payload fields. Watch for missing values caused by renamed fields, logic branches that change behavior when a condition evaluates differently against a new field path, and outbound payloads sent to external systems that may also need to match the new field names.

Related Content

Qlik Cloud Webhooks - Migration to new event formats is coming 

Environment

• Qlik Cloud
• Qlik Automate

The information in this article is provided as-is and will be used at your discretion. Depending on the tool(s) used, customization(s), and/or other factors, ongoing support on the solution below may not be provided by Qlik Support.

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 

Note that in October 2022, a set of Microsoft patches interfered with SSL handshakes. See Qlik Sense Enterprise on Windows: Internal Error while accessing Data Load Editor, Data Manager, and creating a new App for details.

The Qlik Sense Data Manager and Data Connection do not load when opening the Data Load Editor or Add Data Wizard. The Qlik Sense hub does not load a data connection, or takes too long to load it.

This issue happens predominantly in Deployments within Environments with restricted Internet access. The workaround is to remove the Custom Data Connectors from the installation folder.

Other symptoms might include:

• ErrorCode.11041 occurs when opening up an App
• ErrorCode.11043 occurs when creating a Database connection in the data load editor.

Another possible symptom and root cause is:

• After changing the Domain or service user, all connectors are unavailable, even the existing data connections, which are marked "Unknown Connection type" in the data load editor. Reloading apps also fails.
• The connector error shows "Handling QVX_GET_EXECUTE_ERROR", and Proxy log shows "Authentication failed because the remote party closed the transport stream".

Cause

Qlik connectors are cryptographically signed for authenticity verification. The .NET framework verification procedure used for this signing includes checking OCSP and Certificate Revocation List information, which are fetched from an online resource if the system doesn't have a cached local copy. These requests will timeout due to a lack of access to online resources in environments with restricted, slow, or no internet connection. Due to an authenticity check failure, the connector will not run, and the app reload fails.

Resolution

Verify if your system is affected by Microsoft patches interfering with SSL handshakes. See Qlik Sense Enterprise on Windows: Internal Error while accessing Data Load Editor, Data Manager, and creating a new App.

If you are not affected by the SSL handshake issue, proceed with one of the below workarounds.

Workaround 1

Follow the instructions ad documented in An error occurred / Failed to load connection error message in Qlik Sense - Server Has No Internet 

Workaround 2

Enable internet access. 

Alternatively, using a third-party tool such as Fiddler or built-in browser debug tools, identify the addresses used and add them to allow lists on firewalls/proxies, otherwise blocking internet traffic. 

Workaround 3

Temporarily move the following files outside of Program Files:

• OvOdbcConnectorPackage and OvDataMarketConnector 

Files can be found in: C:\Program Files\Common Files\Qlik\Custom Data

In a multi node environment, please do it for all the nodes. You can also try removing only the OvOdbcConnectorPackage, as the OvDataMarketConnector does not always fail. 

Note that when moving the files, you will not be able to use the Data Market Connector or the ODBC Package. 

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