After upgrading to Qlik Sense Enterprise on Windows May 2023 (or later), the Qlik Sense Repository Service may cause CPU usage spikes on the central node. In addition, the central Engine node may show an increased average RAM consumption while a high volume of reloads is being executed. 

The Qlik Sense System_Repository log file will read:

"API call to Engine service was successful: The retrieved 'StaticByteSize' value for app 'App-GUID' is: 'Size in bytes' bytes." 

Default location of log: C:\ProgramData\Qlik\Sense\Log\Repository\Trace\[Server_Name]_System_Repository.txt

This activity is associated with the ability to see the Base memory size in the Qlik Sense Enterprise Management Console. See Show base memory size of apps in QMC.

Resolution

The feature to see Base memory size can be disabled. This may require an upgrade and will require downtime as configuration files need to be changed.

Take a backup of your environment before proceeding.

1. Verify the version you are using and verify that you are at least on one of the versions (and patches) listed: 
   
   
   • May 2023 Patch 13
   • August 2023 Patch 10
   • November 2023 Patch 4 
   • February 2024 IR
     
2. Back up the following files:
   
   
   • C:\Program Files\Qlik\Sense\CapabilityService\capabilities.json
   • C:\Program Files\Qlik\Sense\Repository\Repository.exe.config
     
     *where C:\Program Files can be replaced by your custom installation path.
     
     
3. Stop the Qlik Sense Repository Service and the Qlik Sense Dispatcher Service
   
4. Open and edit the capabilities.json with a text editor (using elevated permissions)
   1. Open C:\Program Files\Qlik\Sense\CapabilityService\capabilities.json
   2. Locate: "enabled": true,"flag": "QMCShowAppSize"
   3. Change this to: "enabled": false,"flag": "QMCShowAppSize"
   4. Save the file  
5. Open and edit the repository.exe.config with a text editor (using elevated permissions)
   1. Open C:\Program Files\Qlik\Sense\Repository\Repository.exe.config
   2. Locate: </appSettings>
   3. Before the </appSettings> closing statement, add:
      <add key="AppStaticByteSizeUpdate.Enable" value="false"/>
   4. Save
6. Start all Qlik Sense services
7. Verify you can access the Management Console

If any issues occur, revert the changes by restoring the backed up files and open a ticket with Support providing the changed versions of repository.exe.config, capabilities.json mentioning this article. 

Related Content

Show base memory size of apps in QMC

Internal Investigation:

QB-22795
QB-24301

Environment

Qlik Sense Enterprise on Windows  May 2023, August 2023, November 2023, February 2024. 

This article aims to help you facilitate the most effective way to collaborate with Qlik Support. It defines your responsibilities as a partner, including reproducing issues, performing basic troubleshooting, and consulting the knowledge base or official documentation.

Before contacting Qlik Talend Technical Support, partners must complete the steps outlined in Qlik Responsible Partner Duties and should review the OEM/MSP Support Policy to understand the scope of support and the expectations on Partners.

• Partners are required to complete the steps outlined in this article before submitting a support case.
• It is the partner’s responsibility to answer the customer's questions to the best of their ability by referring to documentation, the Qlik Community, previous cases, and online resources before submitting a case or commenting on an existing one.
• For high-priority or urgent issues, it is acceptable to raise a ticket early. However, the responsibilities outlined in the article still apply at every stage of the case.

Content

• General Expectations Before Submitting a Case
• Provide Product and Version Information
• Reproduce the Issue in Your Environment
• Always Provide Complete (Not Partial) Logs
• Describe What You Have Already Investigated
• Submit All Related Files You Investigated Or Used For Replication
• Submit the Case Using Your Partner Account
• Partner Case Submission
• Partner Case Submission Template
• Summary of the Problem
• Customer Information
• Files Attached

General Expectations Before Submitting a Case

Isolate What Is Affected

Identify which Qlik product, source endpoint, target endpoint, environment, or system layer is experiencing the issue.

For example, if a task fails in Qlik Replicate on Windows, check whether the issue occurs in a single task or across all tasks, whether it happens during full load or CDC, and whether it is related to a specific table or the data itself.

Similarly, if the issue occurs in only one environment (e.g., Production), ask the customer to confirm whether it can be reproduced in a test environment, or test in your own environment to determine if the issue is environment-related.

Provide Product and Version Information

Always include the exact product name, version, source endpoint, target endpoint the customer is using. 

Many issues are version-related, endpoint-related and Support cannot accurately investigate the issue without this information.

If the product the customer is using has reached End of life (EOL), please plan the upgrade. If the issue can be reproducible on the latest version, please reach out to us so that we can investigate and determine whether it's a defect or working as designed. 

For End of Life or End of Support information, see Product Lifecycle

Reproduce the Issue in Your Environment

Partners are expected to recreate the customer’s environment (matching versions, configurations, and other relevant details) and attempt to reproduce the issue.

If you do not already have a test environment, please ensure one is set up. Having your own environment is essential for reproducing issues and confirming whether the same behavior occurs outside of the customer’s setup.

In some cases, it may also be helpful to test in a clean environment to rule out local configuration issues.

If the issue does not occur in the newer version or a clean setup, it may have already been resolved, and you can propose an upgrade as a solution.

See the Release Note for the resolved issues.

Regardless of whether the issue could be reproduced, please include: 

• The exact Qlik Product version and environment you used for testing
• The exact steps you followed
• Screenshots showing your process
• Any sample data, DDL, or setting used during testing
• A summary of your results (such as “Reproduced same error,” or “Could not reproduce – no error occurred”)

Always Provide Complete (Not Partial) Logs

While pasting a portion of the log into the case comment can help highlight the main error, it is still required to attach the Diagnostic Package with the entire original log file (using, for example, FileCloud).

Support requires the full verbose logs and task settings to understand the overall context and verify that the partial information provided is accurate and complete.

It is difficult to verify the root cause or provide reliable guidance without full verbose logs.

Additionally:

• Specify which logs you reviewed(If there are a large number of log files, please specify the exact log file name).
• Confirm that the customer has provided complete, untrimmed logs and decrypted logs if necessary for certain data errors.
• Include logs from both the customer's environment and your own reproduction tests
• Change the log level to VERBOSE temporarily, reproduce the issue, and share the Diagnostic Package with us.
  
  Providing both sets of logs allows Support to understand what tests have been performed and to verify whether the same error occurred during reproduction. 

Describe What You Have Already Investigated

Please do not simply forward or copy and paste the customer’s inquiry.

As a responsible partner, you are expected to perform an initial investigation. In your case submission, clearly describe:

• What have you reviewed (such as logs and configurations)?
• What steps did you take to isolate or reproduce the issue?
• What have you analyzed, tested, or attempted?
• What you concluded or suspected based on your investigation (such as why you think it is a bug, why you think the problem is occurring)

Sharing this thought process:

• Helps Support understand your assumptions
• Avoids duplicated effort
• Demonstrates that the case is ready for advanced-level investigation

Even if the issue is still unresolved, outlining what you have already tried helps Support address it more quickly and effectively.

Submit All Related Files You Investigated Or Used For Replication

Attach all relevant files you have received from the customer and personally reviewed during your investigation, as well as all relevant files you have used when reproducing the steps.

Providing both the customer’s files and your reproduction files enables Support to verify whether the same issue occurs under the same conditions and to determine if the problem is reproducible, environment-specific, or specific to the customer’s configuration.

This includes (but is not limited to):

• Log files (such as server logs, Windows Event logs, job logs)
• Screenshots: If an error appears in the UI, please include screenshots showing the error message or any screenshots that help illustrate the issue
• Sample data that causes the issue
• Affected Table DDL(both source and target)
• Output of change table (ct table)
• Any other relevant information that may help explain the issue
• Including specific details for the issue, such as:
  • The exact time of occurrence
  • Frequency
  • Whether it was a one-time issue or the issue occurs continuously
  • Specific affected table name, column name
  • Specify any triggering conditions or patterns
  • Has anything changed in the environment (including maintenance) or the design of the task
  • If this is related to an upgrade
  • Current status of the issue
  • Background of the issue(such as requirements)

Submit the Case Using Your Partner Account

All support cases must be submitted using your official partner account, not the customer's account.

If you do not yet have a partner's account, contact Qlik Customer Support to request access and to receive the appropriate onboarding.

Partner Case Submission

Review the support policy and set the case severity properly. See Qlik Support Policy and SLAs.

Partner Case Submission Template

This template provides guidance on what to include and how to structure your case.

Summary of the Problem

What happened? When did it happen? Where did it occur?

Clearly describe the issue, including:

• A summary of the impact (example: "Unable to resume the task")
• The exact time of occurrence (example: "Since July 10, from 13:55 JST")
• Product Name:
• Product Version:
• Source Endpoint:
• Source Version/ODBC driver version:
• Target Endpoint:
• Target Version/ODBC driver version:
• Operating System: 
  (Such as Windows Server 2019, RHEL 😎
• LogStream / FileChannel Involved

Specify if applicable:

• Task Type: Existing task / New task
• Environment: Production / Development
• Tenant information(only Qlik Cloud)

Find your Qlik Cloud Subscription ID and Tenant Hostname and ID

Customer Information

Only include what is needed based on the case type.

Files Attached

List the files you’ve included in the case and provide a brief description of each.

Summary of your Investigation

Explain what steps you took to investigate the issue before contacting Support.

Examples:

• Logs/files you have reviewed
• Patterns/errors observed
• Assumptions you made (such as suspected cause)
• Whether the issue is reproducible (If it's reproducible, describe the reproduction steps too)
• Troubleshooting steps attempted
• Expected Result
• Observed Result
• Is there any known workaround?
  (Yes / No – please describe)
• Related Community Discussions
  (Please provide a link to the related community, if available.)
• Document Reference Available:
  (Yes / No – provide link if possible)

Thank you! We appreciate your cooperation in following these guidelines.

This ensures that your cases can be handled efficiently and escalated quickly when necessary.

Environment

• Qlik Data Integration Products

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

Content

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

What's New

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

2.1.0 September 2025 Release Notes

Known Limitations (2.1.0)

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

2.0.0 May 2025 Release Notes

Known Limitations (2.0.0)

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

1.4.0 December 2023 Release Notes

Known Limitations (1.4.0)

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

1.3.0 May 2023 Release Notes

Qlik Sense Enterprise on Windows offers the ability to preload apps. See Creating preload tasks | help.qlik.com for details. This feature was introduced in the May 2024 release. 

When is a preloaded app unloaded? 

The app is automatically unloaded after the combined duration of the App cache time (engine setting) and Time to live (preload task). The timer starts after the app has last been used.

App cache time

To set or verify App cache time:

1. Go to the Qlik Sense Management Console
2. Navigate to the Engine
3. Open the Apps tab
4. Locate App cache time (seconds)
   
   

Time to live

To set or verify Time to live:

1. Go to the Qlik Sense Management Console
2. Go to Tasks
3. Edit the task set to preload
4. Open the Preload tab
5. Locate Time to live (minutes)
   
   

In the provided example, App cache time is set to 30 minutes and Time to live to 10 minutes. The app will unload after not being in use for 40 minutes.

Environment

• Qlik Sense Enterprise on Windows

The HubSection_Home resource filter in Qlik Sense refers to the button which allows a user to navigate back to the Hub from inside of an application.

Default ruleset:

Resolution:

If an administrator should want to disable this functionality for their users, for example, if the application is embedded into another page. Then they will want to disable the default rule named HubSections.

The result with this rule disabled is as follows for the end user:

The result of this change will disable this functionality for all users. If an administrator wants to provide this functionality to a select set of users then the administrator can create a new rule in this schema:

• Resource filter: HubSection_*
• Actions: Read
• Conditions: Some User Condition
  • Example: user.roles like "*Admin*"
    • This will show the Open Hub button for any user who has an Admin role assigned to their user account.
• Context: Both Hub and QMC

You may encounter an error : 400 - Invalid SNI when calling Talend Runtime API (Job as service) after installed 2025-02 patch or later. In the past before the patch version R2025-02 of Talend Runtime Server, it did work well when using the same certificate for SSL connection with Talend Runtime Server and did not cause any issue. 

The SNI validation is active after 2025-02 patch or later.

Resolution

There are three options to slove this issue

1. Obtain and install a proper certificate that references the correct host name and then access it with the hostname rather than by IP.
2. Disable SNI host check.
3. Tell Talend component to resolve IP as hostname

Disable SNI Host Check

This has the same security risk as jetty before it was updated (low security)

In <RuntimeInstallationFolder>/etc/org.ops4j.pax.web.cfg file, please add

jetty.ssl.sniRequired=false

and 

jetty.ssl.sniHostCheck=false

Or configuring these jetty parameters in <RuntimeInstallationFolder>/etc/jetty.xml or jetty-ssl.xml file

• Find the <New class="org.eclipse.jetty.server.SecureRequestCustomizer"> block in your jetty.xml or jetty-ssl.xml 
  
  
• Edit the <Arg name="sniRequired" ...> and <Arg name="sniHostCheck" ...> lines so that the properties' defaults are set to false as shown below:
  
  

  <New id="sslHttpConfig" class="org.eclipse.jetty.server.HttpConfiguration">
  <Arg><Ref refid="httpConfig"/></Arg>
  <Call name="addCustomizer">
  <Arg>
  <New class="org.eclipse.jetty.server.SecureRequestCustomizer">
  <Arg name="sniRequired" type="boolean">
  <Property name="jetty.ssl.sniRequired" default="false"/>
  </Arg>
  <Arg name="sniHostCheck" type="boolean">
  <Property name="jetty.ssl.sniHostCheck" default="false"/>
  </Arg>
  <Arg name="stsMaxAgeSeconds" type="int">
  <Property name="jetty.ssl.stsMaxAgeSeconds" default="-1"/>
  </Arg>
  <Arg name="stsIncludeSubdomains" type="boolean">
  <Property name="jetty.ssl.stsIncludeSubdomains" default="false"/>
  </Arg>
  </New>
  </Arg>
  </Call>
  </New>

  

Resolve IP to Hostname

If the certification includes the domain name, you should use that domain name instead of the IP with the Jetty security updates in Talend Runtime Server.

But if your DNS server does not resolve the IP, you must call it by the IP address, so please check it at first to see if the workaround is feasible for your current situation.

In the examples the hostname is unresolvedhost.net and the IP is 10.20.30.40.

Try this API call at the command line:

curl -k -X GET --resolve unresolvedhost.net:9001:10.20.30.40 https://unresolvedhost.net:9001/services/

or

curl -k -X GET -H "Host: unresolvedhost.net" https://10.20.30.20:9001/services/

If this works, in your Talend component that makes the API call, go to "Advanced settings" or "Headers" table, add a row with Key: Host and Value: The hostname that matches your SSL certificate (e.g. unresolvedhost.net)

This will instruct Talend to send the correct Host header, which most HTTP clients (including Java's HttpClient) will also use as the SNI value during the TLS handshake.
 

Cause

The SNI enforcement is there for a security reason. With the 2025-02 patch, the Jetty components on Talend Runtime Server resolved a CVE security issue where they allowed a hostname to connect to a server that doesn't match the hostname in the server's TLS certificate.

Certificates require the URI not to be localhost or an IP address, and to have at least one dot, so a fully qualified domain name is best.

Related Content 

 https://stackoverflow.com/questions/69945173/org-eclipse-jetty-http-badmessageexception-400-invalid-sni

Environment

Talend ESB 

After configuring the Qlik Stitch user in Snowflake to use key-pair authentication and updating the Stitch destination settings accordingly, existing integrations begin to fail with the following error:

SQL access control error:
Insufficient privileges to operate on schema 'XXXX'.

Permissions are verified to be correct: All role grants and schema privileges are properly configured in Snowflake as documented in Connecting a Snowflake Destination to Stitch.

Switching back to password authentication restores the integrations, but does not satisfy security requirements for connecting to Snowflake.

Resolution

Run the following SQL command in Snowflake:

ALTER USER STITCH_USER SET DEFAULT_ROLE = STITCH_ROLE;

This ensures the default role is automatically used when connecting via key-pair authentication.
If no role is explicitly defined during login, Snowflake will use STITCH_ROLE by default.

Cause

The issue might occur if Qlik Stitch is using outdated schema references or if the Stitch user’s privileges have changed after switching to key-pair authentication.

Environment

• Qlik Stitch

This article gives an overview of exporting the Qlik Sense apps from the source to a target shared space for backup purposes using Qlik Application Automation.

It explains a basic example of a template configured in Qlik Application Automation for this scenario.

You can make use of the template which is available in the template picker. You can find it by navigating to Add new -> New automation -> Search templates and searching for 'Export an app to a shared space as a backup' in the search bar and clicking on the Use template option in order to use it in the automation.

You will find a version of this automation attached to this article: "Export-app-to-shared-space.json". More information on importing automations can be found here.

Full Automation

Variables used in the template:

1. SourceSpaceID: The variable used to define source space ID. Please provide a shared space ID since copying an app from managed space is not permitted.
2. TargetSpaceID: The variable used to define target space ID. Please provide a shared space ID since copying an app to managed space is not permitted.
3. AppCount: The variable is used to get the count of apps exported to the target space successfully. Initially set this variable to 0.

Automation structure:

1. Add the 'List Apps' block to get all the existing apps in the target shared space. Configure it to use the TargetSpaceID variable as the Space ID.
2. Add the 'Get Space' block to fetch the details of the source shared space. Configure it to use the SourceSpaceID variable as the Space ID.
3. Add the 'List Apps' block to get all the existing apps in the source shared space. Configure it to use the SourceSpaceID variable as the Space ID.
4. Add the 'Filter List' block to get the apps that already exist in the target shared space.
5. Add the 'Condition' block to check if there are any apps from the source shared space that already exist in the target shared space. 
   1. If the condition block outcome evaluates to true:
      • Add the 'Delete App' block to remove the previous version of the source app from the target shared space.
      • Add the 'Copy App' block to copy the app from the source shared space to the target shared space.
      • Add the 'Condition' block to check if the app from the source shared space was successfully exported to the target shared space.
      • If yes, Add 1 to the 'AppCount' variable during each iteration. This variable will provide the total number of apps that have been backed up to the target shared space.
   2. If the condition block outcome evaluates to false:
      • Add the 'Copy App' block to copy the app from the source shared space to the target shared space.
      • Add the 'Condition' block to check if the app from the source shared space was successfully exported to the target shared space.
      • If yes, Add 1 to the 'AppCount' variable during each iteration. This variable will provide the total number of apps that have been backed up to the target shared space.
6. Add the 'Condition' block to check if there are any apps that were exported to the target shared space successfully.
7. If yes, add an 'Update Run Title' block to specify the number of apps that have been exported to the target shared space successfully. The job title is visible when looking at the automation history and My Automation Runs Overview. For more info: Update run title block | Qlik Cloud Help 

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.

Related Content

Export Qlik Sense Apps to GitHub

Environment

Qlik Cloud 
Qlik Automate 

Running a Target Exec of a Qlik Talend Runtime (OSGi) build type artifact fails in Studio with the following:

Execution failed :java.lang.Exception: Job was not built successfully, please check the logs for more details available on C:/Talend/Talend8/Talend8Workspace/ESB2/poms/jobs/process/testmicroservice_0.1/lastGenerated.log

[Job was not built successfully, please check the logs for more details available on C:/Talend/Talend8/Talend8Workspace/ESB2/poms/jobs/process/testmicroservice_0.1/lastGenerated.log

The lastGenerated.log will contain messages similar to:

[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.example.esb2.service:TestMicroservice:bundle:0.1.0
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.apache.commons:commons-lang3:jar -> version 3.10 vs 3.17.0 @ line 171, column 17
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
[WARNING] The requested profile "signature" could not be activated because it does not exist.
[INFO]
[INFO] -------------< org.example.esb2.service:TestMicroservice >--------------
[INFO] Building ESB2 TestMicroservice-0.1.0 (0.1,Job Designs) Bundle 0.1.0
[INFO] from pom.xml
[INFO] -------------------------------[ bundle ]-------------------------------
[INFO]
[INFO] --- osgihelper:8.0.11:generate (osgi-helper) @ TestMicroservice ---
[INFO] Resolve mvn:org.example.esb2.service/TestMicroservice/0.1.0
[INFO]
[INFO] --- resources:3.3.1:resources (default-resources) @ TestMicroservice ---
[INFO] Copying 2 resources from src\main\resources to target\classes
[INFO]
[INFO] --- compiler:3.11.0:compile (default-compile) @ TestMicroservice ---
[INFO] Not compiling main sources
[INFO]
[INFO] --- resources:3.3.1:testResources (default-testResources) @ TestMicroservice ---
[INFO] Not copying test resources
[INFO]
[INFO] --- compiler:3.11.0:testCompile (default-testCompile) @ TestMicroservice ---
[INFO] Not compiling test sources
[INFO]
[INFO] --- surefire:3.3.0:test (default-test) @ TestMicroservice ---
[INFO] Tests are skipped.
[INFO]
[INFO] --- bundle:6.0.0:bundle (default-bundle) @ TestMicroservice ---
[WARNING] Bundle org.example.esb2.service:TestMicroservice:bundle:0.1.0 : Invalid package name: '@BundleConfigExportPackage@' in Export-Package
[WARNING] Bundle org.example.esb2.service:TestMicroservice:bundle:0.1.0 : Invalid package name: '@BundleConfigImportPackage@' in Import-Package
[INFO] Building bundle: C:\Talend\Talend8\Talend8Workspace\ESB2\poms\jobs\process\testmicroservice_0.1\target\TestMicroservice-bundle-0.1.0.jar
[INFO] Writing manifest: C:\Talend\Talend8\Talend8Workspace\ESB2\poms\jobs\process\testmicroservice_0.1\target\classes\META-INF\MANIFEST.MF
[INFO]
[INFO] --- assembly:3.6.0:single (default) @ TestMicroservice ---
[INFO] Reading assembly descriptor: C:\Talend\Talend8\Talend8Workspace\ESB2\poms\jobs\process\testmicroservice_0.1/src/main/assemblies/assembly.xml
[WARNING] The following patterns were never triggered in this artifact inclusion filter:
o 'org.example.esb2.service:TestMicroservice:jar:0.1.0'

[INFO] Building jar: C:\Talend\Talend8\Talend8Workspace\ESB2\poms\jobs\process\testmicroservice_0.1\target\TestMicroservice-bundle-0.1.0.jar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4.650 s
[INFO] Finished at: 2025-10-23T09:12:57-04:00
[INFO] ------------------------------------------------------------------------
[WARNING] The requested profile "signature" could not be activated because it does not exist.

Resolution

Change Build Type to Microservice.

1. Navigate to the Job 
2. Switch to the Deployment tab
3. Change Build Type to Microservice
   
   

Cause

The Remote Engine cannot run Talend Runtime (OSGi) build type artifacts. Therefore, Target Exec is not supported.

Environment

• Qlik Talend Studio

A Qlik Stitch Jira Integration encounters the following error during extraction:

500 JiraInternalServerError The server encountered an unexpected condition which prevented it from fulfilling the request.
...
CRITICAL HTTP-error-code: 500, Error: Internal server error
...
tap_jira.http.JiraInternalServerError: HTTP-error-code: 500, Error: Internal server error

Resolution

Check Jira status page: https://status.atlassian.com/

If there are no active incidents and the error is recurring, please reach out to Jira Support and request to review the logs of your authorizing Jira account. The Jira Support team should be able to provide more insight into these occurrences. Jira Support can be reached at: https://support.atlassian.com/ 

In the event that they suggest Stitch needs to make specific accommodations, please reach out to Qlik Support and provide the details. 

Cause

The Stitch Jira integration utilizes the JIRA Cloud REST API v2, which uses the standard HTTP status codes. 

A 500 error generally indicates an issue with Jira's server(s). The integration has built-in retry logic to account for connection errors returned without an API response from Jira's server(s). 

Ultimately, this error indicates that the Jira server was unable to complete our request. The 500 response is a raw error message from Jira that the extractions will capture in the logs. 

Environment

• Qlik Stitch

A NetSuite Suite Analytics integration encounters the following error: 

Failed to login using TBA

Resolution

Qlik Stitch supports connecting to NetSuite2 (netsuite2.com) through token based authentication.

To use token based authentication, select the Use token based authenitcation option in your integration settings:

Note that this setting cannot be modified once the integration runs an extraction. If you are seeing this error in existing integration(s), you will need to create new ones with token based authentication selected.

For guidance on re-using schema names, see Qlik Stitch: How to Upgrade the Integration to Latest Version with Same Destination Schema. 

Cause

NetSuite Suite Analytics has deprecated netsuite.com in favor of netsuite2.com. Token based authentication is required for a successful connection to netsuite2.com.

Environment

• Qlik Stitch

Due to a recent incident in the US-EAST-1 region, customer tenants may report inaccurate data movement capacities. 

In certain conditions, the capacity for data movement tasks (Landing, Replication, and Lake Landing tasks) has been overreported. As a result, Qlik will not charge affected customers overage for the month of October 2025.

The incident only concerns the capacity metric (data moved) used for consumption and billing, and does not affect the operation of data movement or any other tasks.

What action do I need to take?

No action is required by you to resolve the incident. Qlik is developing a fix to resolve telemetry data collection that will roll out in the coming weeks. The fix will resolve data movement capacity capture moving forward; however, historical telemetry data will not be adjusted.   

During deployment of the fix, users may see data movement tasks briefly show as 'recoverable error' in the monitoring interfaces. This is a standard monitoring assertion built into Qlik Cloud that serves as a warning and does not impact the pipelines running in your gateway.

For any questions or concerns, please contact Qlik Support or your account representative

Environment

• Qlik Talend Cloud

This article provides an overview of how to send straight table data to email as an HTML table using Qlik Automate.

The template is available on the template picker. You can find it by navigating to Add new -> New automation -> Search templates and searching for 'Send straight table data to email as table' in the search bar, and clicking the Use template option.

You will find a version of this automation attached to this article: "Send-straight-table-data-to-email -as-HTML-table.json".

Content:

• Full Automation
• Automation structure
• Related Content

Full Automation

Automation structure

The following steps describe how to build the demo automation: 

1. Add a variable called 'EmailBody' to build the email body, and append the body opening tag and opening text of the email as value to this variable.
   
   
2. Add another variable called 'EmailStraightTable' and append the table opening tag together with the table header opening tag as a value to this variable.
   
   
3. Use the 'Get Straight Table Data' block from the Qlik Cloud Services connector to get data from the straight table for a specific app to be sent as an email. Specify app ID, Sheet ID, and Object ID input parameters. You can use the do-lookup functionality to find value for all these parameters. There is a limit of 100,000 records that can be retrieved through the 'Get Straight Table Data' block. This block will not work with other table types.
   
   
4. Add a 'Loop' block to loop over the keys from the 'Get Straight Table Data' block response which act as the headers of the HTML table. Use the '{getkeys: {$.GetStraightTableData}}' formula in the 'Loop' block.
   
   
5. Add the key/column name as the header of the HTML table in the 'EmailStraightTable' variable block. Outside the loop, add the 'EmailStraightTable' variable block, and append the table header closing tag, and table body opening tag as values to this variable.
   
   
6. Add a 'Loop' block to loop over all the values from the 'Get Straight Table Data' block response. Within the 'Loop' block add the following blocks:
   
   
   1. Use the 'EmailStraightTable' variable block and append the table row opening tag as a value to this variable.
   2. Use another 'Loop' block to loop over all values from the straight table for the current key/ column of the straight table.
   3. Next, use the 'EmailStraightTable' variable block and append the table data opening tag along with the column value for the corresponding key from the straight table which ultimately gives a single row with values for all the keys in each iteration and the table data closing tag as value to this variable.
   4. Use the 'EmailStraightTable' variable block and append the table row closing tag as a value to this variable.
      
      
7. Add the 'EmailStraightTable' variable block and append the table body closing tag with table footer tags as a value to this variable.
   
   
8. Add the 'EmailBody' variable block and append the 'EmailStraightTable' variable, which contains the final HTML table with straight table data, together with the email footer, and body closing tag as a value to this variable.
   
   
9. Add a 'Send Mail' block from the Mail connector to send an email with the above constructed HTML table that contains straight table data. Specify values for all the mandatory input parameters. Please connect to the SMTP server by adding a connection to the Mail connector.

An example output of the email sent:

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

Related Content

How to export more than 100k cells using Get Straight Table Data Block 

Environment

• Qlik Cloud Analytics
• Qlik Automate

Environment

• Qlik Sense Enterprise SaaS
• Qlik Application Automation

This article describes how an Excel file can be sent as an attachment by using the Send Mail block in Qlik Application Automation.

Automation Structure

The creation of an Excel report from a Qlik Sense straight table is explained in the first part of this article.

Let's walk through the blocks used in the automation workflow to send the Excel file as an attachment using the "Send Mail" block.

1. Open the Excel file saved in Microsoft SharePoint using the "Open File on Microsoft SharePoint" block.
   
   
2. Use the "Send Mail" block from Mail Connector to send the Excel file as an attachment via email.
   
   
   

A JSON file containing the above automation is attached to this article.

Please follow the steps provided in the How to import automation from a JSON file article to import the automation.

Related Content 

• Generate Excel Report 
• Copy data from a Qlik Sense straight table to an Excel sheet 

This article describes how to handle dynamic tables in Qlik Replicate, such as when source tables are frequently added and deleted. This avoids having to manually add the table to a task each time.

The methods described will work for most source endpoints. 

Our example uses Oracle as the source.

1. Select the pattern in the Table Section
   Make sure the task is set to Full Load + CDC
   
   
   
   
2. Review the list of tables for the selected pattern under Full Table List
   
   
   
   
3. After the initial load, the tables are successfully created at the target:
   
   
   
   

4. Create a new table in the source:
   
   create table SYSTEM.suri4(id int primary key, anane varchar(10))
   
   

5. The table is automatically added to the task
   
   
   
   CDC Status:
   
   
   
   Log Entry:
   
   
   
   Table entry in the target:
   
   
   
   
6. Drop table from the Source:
   
   drop table SYSTEM.suri4;
   
   
7. The table is automatically dropped from the target. We can observe the Drop DDL command entry in the log:
   
   
   

Environment

• Qlik Replicate

The client Secret for a Single Sign-On Solution has expired. 

After successfully logging in with a recovery address (https:// YOUR-TENEANT .eu.qlikcloud.com/login/recover) using the Service Account Owner (SAO) account, logging in to the Qlik Cloud Administration Console fails with:

User allocation required You do not have a valid user allocation. Please contact an administrator for more information

Resolution

Once you successfully log in to the tenant via recovery link using the SAO (Service Account Owner) credentials, either navigate to the Qlik Cloud Administration Console by using

• the Settings icon
• or by directly using https://mytenant.eu.qlikcloud.com/console

This will allow you to access the Qlik Cloud Administration Console and update the client secret for your IDP settings.

Environment

• Qlik Cloud Analytics

Related Content

• Qlik Cloud: The provided client secret keys are expired. Visit the Azure Portal to create new keys for your app

Generating an API key fails with:

An error occurred when generating the API Key. Please try again.

Resolution

1. Open the Tenant Management Console (TMC)
2. Navigate to Administration > Manage Users (A) > Permissions (B)
3. Click Create new (C)
   
   
   
   
4. In the Create new role section, name the role and:
   1. Open Features and actions
   2. Switch Managed API keys to Allowed
   3. Click Confirm
      
      
      
      
5. Assign users to the new role as needed. See Assigning security roles and custom roles to groups for details. 

Cause

The user does not have a role with the required permission.

The old Developer role will be deprecated. Follow the steps in this article to future proof your system and create a custom role.

Related Content

• Managing custom roles | Qlik Cloud Help 
• Assigning security roles and custom roles to groups | Qlik Cloud Help 

Environment

• Qlik Cloud Analytics

This article explains how you can Delete spaces in Qlik Cloud Services using Qlik Automate. Multiple spaces can be deleted during one run. As when deleting a space via the user interface, this will also delete any apps, data files or other content within the space(s) using the relevant blocks for those content types.

For information about spaces in Qlik Cloud, see Navigating Spaces.

This automation is not designed to be triggered using a webhook or on a schedule. It has been designed with manual user input in mind and requires multiple confirmations.

If you use your own automation to delete spaces, know that deleting a space via the space blocks will not delete the content in the space, and will instead result in that content being orphaned in the tenant. Leverage the examples in this automation to first delete content from spaces prior to deleting the space.

Once deleted, spaces, apps, or data files cannot be recovered.

Content:

• Prerequisites
• Overview
• Start
• Confirm selected spaces
• Delete apps
• Delete data files
• Delete spaces
• Finalize
• Running the Automation
• Related Content

Prerequisites

This automation assumes you have a TenantAdmin role.

Overview

The automation is divided into five sections: 

1. Start 
2. Confirm selected spaces
3. Delete apps
4. Delete data files
5. Delete spaces
6. Finalize

Start

The Start section retrieves all available spaces and prompts you to select what spaces you want to delete.

Overview:

Setting it up:

1. The List Spaces block retrieves all spaces on the tenant that you have access to.
2. The Filter List block filters spaces that you have the delete permission to.
   
   This is achieved using a condition configured such as this:
   
   Condition
   If meta.actions
   list contains
   delete
   
   
   
   
3. The Transform List block reformats the space list to improve readability in the input block (id, name and type are kept).
   
4. The Inputs block adds a prompt for selecting the spaces to delete.
   
   Multi-selection is allowed:
   
   
   
   
5. A Go To Label block moves to the next section of the automation.
    
   Before the Go To Label block can be configured, the targeted Label must already exist. This is done in the next section.

Confirm selected spaces

This section provides the possibility to review the selected spaces before deleting them.

Overview:

Setting it up:

1. The Label block is named Confirm Selected Spaces and this must also be configured in the Go To Label block from the previous section.
2. A Loop block loops over selected spaces.
3. Within the loop, a List Apps block retrieves apps in the space. The output of this block is stored in the variable appList which is used for reviewing what apps exist within the spaces that will be deleted.
4. To retrieve the connectionId for data files in this space, a Raw API Request block is used. The path in the block is configured to use data-files/connections and the HTTP method is set to GET. A query parameter is also added where the key is set to spaceId and the value is set to {$.loop.item}.
5. The connectionId retrieved in the previous step is used to retrieve data files in this space using the List Data Files block. The output of this block is stored in the variable dataFileList which is used to review the data files that exist within the spaces flagged for deletion.
6. After the loop, an Output block displays which spaces will be deleted.
7. We use an Inputs block to allow user confirmation before deleting apps, data files and other content within the selected spaces:
   
   
   
   
8. A Go To Label block moves to the next section of the automation.
   
   Before the Go To Label block can be configured, the targeted Label must already exist. This is done in the next section.
   

Delete apps

Once deleted, spaces, apps, or data files cannot be recovered.

This section deletes all existing apps inside the space(s). A space cannot be removed before all apps are deleted.

Overview:

Setting it up:

1. The numeric variable iter tracks how many apps are deleted. 
2. A Loop block loops over the items in the variable appList.
3. The variable iter is increased by 1 per loop iteration.
4. The block Get App Information retrieves the app name based on the app id. 
5. The app is deleted using the block Delete App.
6. A deleted app status will be presented using the string variable message. 
7. The delete apps status will be presented using an Output block:
   
   
   
   
8. The delete apps status will also be presented using the block Update Run Title:
   
   
   
   
9. A Go To Label moves on to the next section of the automation. 
   
   Before the Go To Label block can be configured, the targeted Label must already exist. This is done in the next section.

Delete data files

Once deleted, spaces, apps, or data files cannot be recovered.

This section deletes all data files within the selected space(s).

Overview:

Setting it up:

1. The numeric variable iter tracks of how many data files are deleted. 
2. A Loop block loops over the items in the variable dataFileList.
3. The variable iter is increased by 1 per loop iteration.
4. To retrieve the data file name for datafiles we use a Raw API Request block configured such as this:
   
   Path: data-files/{ $.loop3.item }
   
   HTTP Method: GET
   
   
   
   
5. The data file is deleted using the block Delete Data File.
6. A deleted data file status will be presented using the string variable message. 
7. The deleted data file status will be presented using an Output block:
   
   
   
   
8. The delete data file status will also be presented using the block Update Run Title:
   
   
   
   
9. Finally, a Go To Label block moves on to the next section of the automation. 
   
   Before the Go To Label block can be configured, the targeted Label must already exist. This is done in the next section.

Delete spaces

Once deleted, spaces, apps, or data files cannot be recovered.

This section deletes all selected spaces. 

Overview:

Setting it up:

1. The numeric variable iter tracks of how many spaces are deleted. 
2. A Loop block loops over the selected spaces.
3. The variable iter is increased by 1 per loop iteration.
4. To retrieve the name of the space we use a Lookup Item In List block.
5. The space is deleted using the block Delete Space.
6. A deleted space status will be presented using the string variable message.
7. The delete space status will be presented using an Output block
   
   
   
   
8. The delete space status will also be presented using the block Update Run Title.

Finalize

This section wraps up the automation and updates the final status of the automation run. 

Overview:

Setting it up:

1. A summary of how many apps, data files and apps have been deleted is presented using the string variable message.
2. The summary is presented using an Output block:
   
   
   
   
3. The summary is also returned using the block Update Run Title:
   
   

Running the Automation

1. On run, choose which space to delete. Be careful not to select spaces you want to keep:
   
   
   
2. Once you have selected the space or spaces, you are prompted to confirm the deletion of apps, data files and other content that exists within this space or spaces. If you don't want to proceed you can stop the automation. If you want to proceed you need to click on the green confirmation button:
   
   

Related Content

Navigating Spaces
Managing permissions in shared spaces 
Managing permissions in managed spaces 

Environment

Qlik Automate
Qlik Cloud

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.

Is it possible to upgrade windows server OS on the same machine where Qlik Sense, QlikView, or Qlik NPrinting are installed?
How will Windows Update and Windows Service packs affect Qlik Products?

Questions often arise when upgrading or applying Windows Service packs or running Windows Update, e.g. "Will applying service packs or patches from Microsoft affect installed Qlik software or clients?"

Typically upgrading Windows or applying patches or installing Window Service packs should not affect any installed Qlik products. As a precaution to prevent unexpected effects, below practices are recommended.

General best practices to prepare for updates include:

• Create a Windows Operating System Restore Point (for patches/updates)
• Create a backup of the Qlik environment. See How to take a backup and restore Qlik Sense, What files to include in Backup for QlikView, or Backing up Qlik Nprinting.
• If using certificates, backup the available certificates.
• Make sure your security, account, and GPO settings won´t be overwritten on windows level after the upgrade. Changes to security and account settings due to the GPO can affect service account permissions.
• If a VM or other virtualization technology is in use, take a snapshot.

If you have general questions regarding compatibility of host operating systems, please review the release notes for your release. If you have questions regarding specific patches, raise this query directly in the relevant Qlik product forums.

Qlik Sense Enterprise Client-Managed offers a range of Monitoring Applications that come pre-installed with the product.

Qlik Cloud offers the Data Capacity Reporting App for customers on a capacity subscription, and additionally customers can opt to leverage the Qlik Cloud Monitoring apps.

This article provides information on available apps for each platform.

Content:

• Qlik Cloud
• Data Capacity Reporting App
• Access Evaluator for Qlik Cloud
• Answers Analyzer for Qlik Cloud
• App Analyzer for Qlik Cloud
• Automation Analyzer for Qlik Cloud
• Entitlement Analyzer for Qlik Cloud
• Reload Analyzer for Qlik Cloud
• Report Analyzer for Qlik Cloud
• How to automate the Qlik Cloud Monitoring Apps
• Other Qlik Cloud Monitoring Apps
• OEM Dashboard for Qlik Cloud
• Monitoring Apps for Qlik Sense Enterprise on Windows
• Operations Monitor and License Monitor
• App Metadata Analyzer
• The Monitoring & Administration Topic Group
• Other Apps

Qlik Cloud

Data Capacity Reporting App

The Data Capacity Reporting App is a fully supported app distributed within the product. For more information, see Qlik Help.

Access Evaluator for Qlik Cloud

For more information, see Qlik Cloud Access Evaluator.

Answers Analyzer for Qlik Cloud

For more information, see Qlik Cloud Answers Analyzer.

App Analyzer for Qlik Cloud

For more information, see Qlik Cloud App Analyzer.

Automation Analyzer for Qlik Cloud

For more information, see Qlik Cloud Automation Analyzer.

Entitlement Analyzer for Qlik Cloud

The Entitlement Analyzer is a Qlik Sense application built for Qlik Cloud, which provides Entitlement usage overview for your Qlik Cloud tenant for user-based subscriptions.

The app provides:

• Which users are accessing which apps
• Consumption of Professional, Analyzer and Analyzer Capacity entitlements
• Whether you have the correct entitlements assigned to each of your users
• Where your Analyzer Capacity entitlements are being consumed, and forecasted usage

For more information, see The Entitlement Analyzer.

Reload Analyzer for Qlik Cloud

For more information, see Qlik Cloud Reload Analyzer.

Report Analyzer for Qlik Cloud

For more information, see Qlik Cloud Report Analyzer.

How to automate the Qlik Cloud Monitoring Apps

Do you want to automate the installation, upgrade, and management of your Qlik Cloud Monitoring apps? With the Qlik Cloud Monitoring Apps Workflow, made possible through Qlik's Application Automation, you can:

1. Install/update the apps with a fully guided, click-through installer using an out-of-the-box Qlik Application Automation template. 
2. Programmatically rotate the API key that is required for the data connection on a schedule using an out-of-the-box Qlik Application Automation template. This ensures that the data connection is always operational. 
3. Get alerted whenever a new version of a monitoring app is available using Qlik Data Alerts. 

For more information and usage instructions, see Qlik Cloud Monitoring Apps Workflow Guide.

Other Qlik Cloud Monitoring Apps

OEM Dashboard for Qlik Cloud

For more information and to download the app and usage instructions, see Qlik Cloud OEM Dashboard & Console Settings Collector.

With the exception of the Data Capacity Reporting App, all Qlik Cloud monitoring applications are provided as-is and are not supported by Qlik. Over time, the APIs and metrics used by the apps may change, so it is advised to monitor each repository for updates and to update the apps promptly when new versions are available.

If you have issues while using these apps, support is provided on a best-efforts basis by contributors to the repositories on GitHub.

Monitoring Apps for Qlik Sense Enterprise on Windows

Operations Monitor and License Monitor

The Operations Monitor loads service logs to populate charts covering performance history of hardware utilization, active users, app sessions, results of reload tasks, and errors and warnings. It also tracks changes made in the QMC that affect the Operations Monitor.

The License Monitor loads service logs to populate charts and tables covering token allocation, usage of login and user passes, and errors and warnings.

For a more detailed description of the sheets and visualizations in both apps, visit the story About the License Monitor or About the Operations Monitor that is available from the app overview page, under Stories.

Basic information can be found here:

The License Monitor 
The Operations Monitor 

Both apps come pre-installed with Qlik Sense. 

If a direct download is required: Sense License Monitor | Sense Operations Monitor. Note that Support can only be provided for Apps pre-installed with your latest version of Qlik Sense Enterprise on Windows. 

App Metadata Analyzer

The App Metadata Analyzer app provides a dashboard to analyze Qlik Sense application metadata across your Qlik Sense Enterprise deployment. It gives you a holistic view of all your Qlik Sense apps, including granular level detail of an app's data model and its resource utilization.

Basic information can be found here: 

App Metadata Analyzer (help.qlik.com)

For more details and best practices, see: 

App Metadata Analyzer (Admin Playbook)

The app comes pre-installed with Qlik Sense.

The Monitoring & Administration Topic Group

Looking to discuss the Monitoring Applications? Here we share key versions of the Sense Monitor Apps and the latest QV Governance Dashboard as well as discuss best practices, post video tutorials, and ask questions.

Monitoring & Administration 

Other Apps

LogAnalysis App: The Qlik Sense app for troubleshooting Qlik Sense Enterprise on Windows logs 
Sessions Monitor, Reloads-Monitor, Log-Monitor 
Connectors Log Analyzer 

All Other Apps are provided as-is and no ongoing support will be provided by Qlik Support.