After replacing an expired SSL certificate on a Qlik Sense Client-Managed environment, on-premises / desktop browser access works correctly. However, the Qlik Sense Mobile app (both iOS and Android) displays an “invalid certificate” or “not secure” error and does not show the login screen.

Invalid certificate / This certificate is not secure

Mobile browsers on the same devices can reach the hub and display the login page without issues.

Environment:

• Qlik Sense Enterprise on Windows (Client Managed)
• Qlik Sense Mobile app (iOS and Android)
• SSL certificate issued by GoDaddy (especially newer R1 intermediate certificates)

Resolution

The Qlik Sense Mobile app is stricter about certificate chain validation than most mobile browsers. An incomplete chain causes the app to reject the connection even when browsers accept it.

1. From a machine that can reach the Qlik Sense server, run the following command and review the output: openssl s_client -connect yourserver.domain.com:443 -showcerts
2. Look for Verify return code: 20 (unable to get local issuer certificate). This indicates the server is not sending the complete chain.
3. Re-download the certificate bundle from GoDaddy, selecting the full chain/bundle option.
4. Confirm the downloaded bundle contains three certificates:
   1. Server (leaf) certificate
   2. GoDaddy TLS Intermediate CA DV – R1v1
   3. GoDaddy R1-to-G2 cross-signed certificate
5. Install the complete bundle on the reverse proxy / IIS / load balancer that terminates SSL for Qlik Sense and re-bind the certificate.
6. Restart the relevant service(s) after binding the new certificate.
7. On the affected mobile devices:
   1. Fully close the Qlik Sense Mobile app (remove it from recent apps/app switcher).
   2. Restart the mobile device.
   3. Reopen the app and try logging in again.

Important: Always verify the full chain with openssl s_client -connect ... -showcerts after making changes. The presence of only two certificates in the chain is a common cause of this issue with newer GoDaddy certificates.

Cause

GoDaddy’s newer certificate hierarchy uses an intermediate certificate named “GoDaddy TLS Intermediate CA DV – R1v1”. This intermediate is not yet trusted by all clients. To maintain compatibility, GoDaddy provides an additional R1-to-G2 cross-signed certificate that links the new intermediate back to a widely trusted root.

When only the leaf certificate and the R1 intermediate are installed (a common default when downloading a basic chain), the server does not present the cross-signed certificate during the TLS handshake.

The result is: Verify return code: 20 (unable to get local issuer certificate)

Most modern mobile browsers already trust the new GoDaddy root and can complete the connection. The Qlik Sense Mobile app, however, performs stricter certificate path validation and requires the complete chain, including the cross-signed certificate. This difference causes the “invalid certificate” / “not secure” error exclusively in the mobile app while desktop and mobile browsers continue to work.

App distribution automatic reloads fail randomly with this error message in the logs (C:\ProgramData\Qlik\Sense\Log\AppDistributionService\Trace😞

Response status code does not indicate success: 401 (Unauthorized).

Some reloads may work correctly, but the error is frequent. The same reloads complete successfully if run manually.

Resolution

Ensure that the time in your Qlik Sense on Windows servers matches the time in Qlik Cloud. This must be verified on every node.

If you are using NTP, please check that it is correctly configured and that the server clock is in sync.

Cause

A common cause for this issue is clock inaccuracy between the Qlik Sense on Windows server and Qlik Cloud. A time difference of even a few seconds can cause token validation to fail intermittently. 

This blocks the communication, and the reload fails.

Environment

• Qlik Sense Cloud
• Qlik Sense Enterprise on Windows (on-premise)

Qlik Replicate task notifications can stop being delivered after the server-level Mail Settings (for example, the SMTP host) are changed.

Since Qlik Replicate loads server-level settings into memory when a task starts, tasks already running when the change is committed continue to send notifications using the previous mail server configuration and will therefore fail.

Environment

• Qlik Replicate

Resolution

To restore notification delivery for the affected tasks:

1. In the Qlik Replicate console, stop all affected tasks
2. Restart the Qlik Replicate services
3. Resume (start) the previously stopped tasks
4. Trigger (or wait for) the next notification condition and confirm that the notification email is received by the configured recipients

To prevent the issue:

Whenever server-level Mail Settings or the SMTP server configuration are changed, restart the affected Qlik Replicate tasks so that they reload the updated configuration. A Qlik Replicate service restart may also be performed as part of the change procedure to ensure the new settings are fully initialized.

Environment

• Qlik Replicate

Using https://www.talend.com/api/get_tis_validation_token_form.php to validate the Talend Administration Center license, the following error is returned:

Data is corrupted: internal error

Resolution

Ensure the link is being used from the Talend Administration Center License validation page accessible from the UI or the DB configuration page.  

A note for Air Gapped / No Internet Access environments:

1. Go to the License Validation Page
2. Obtain the Validation String, copy to Notepad or similar
3. In the same page, right-click the link to the validation string. 
4. Copy the link and paste it into Notepad or similar
   
   The link must contain some unique value in the URL iv=xxxxxxxxxx
   
   
5. Use the validation string and link in an environment with access to archive.talend.com to validate.

Cause

QTAC-1329 changed the validation URL from TIS Validation Token (www.talend.com) (no parameters) to TIS Validation Token (archive.talend.com). This new feature introduced a random IV that is generated together with the validation message.

Environment

• Talend Administration Center

Qlik MCP may need to be regularly reconnected to Claude or other LLMs.

Resolution

Verify that you set offline_access to Allowed during OAuth setup, which reduces the need to re-authenticate once every 30 days.

See Creating OAuth clients for LLM clients for details.

Environment

• Qlik MCP

After upgrading Qlik NPrinting to either May 2026 SR1 or February 2025 SR7, HTML-type reports fail with the following engine log and NPrinting Designer report preview error:

The preview request failed with message: specific argument was out of the range of valid values

System.ThrowHelper.ThrowArgumentOutOfRangeException()

Resolution

This issue is caused by a defect (SUPPORT-11950) in Qlik NPrinting May 2026 SR1 and February 2025 SR7. 

Workaround:

Reduce the resolution of images in the report to lower values (example: 1024x768).

Alternatively, downgrade the Qlik NPrinting Engine. 

• For Qlik NPrinting February 2025: Keep the Qlik NPrinting February 2025 SR7 Server installed, but uninstall the Qlik NPrinting February 2025 SR7 Engine, then install the February 2025 SR6 Engine.
• For Qlik NPrinting May 2026: Keep the Qlik NPrinting May 2026 SR1 Server installed, but uninstall the Qlik NPrinting May 2026 SR1 Engine, then install the May 2026 IR Engine.

Upgrade all components to the fixed version as soon as possible to address the version mismatch.

Fix Version:

Fixes will be available with:

• Qlik NPrinting May 2026 SR2
• Qlik NPrinting February 2025 SR8 

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 SUPPORT-11950 for reference.

Environment

• Qlik NPrinting May 2026 SR1 and February 2025 SR7

Qlik Replicate tasks can be configured to move data from a source DB to a Target DB. These tasks can be configured in a variety of ways to move data from the source to the target database.

This article aims to compare three popular task configurations and will provide additional details for the available Full Load settings. It is a supporting document to the Techspert discussion: Full Load.

Available configurations:

• FULL LOAD only
• CDC only
• FULL LOAD and CDC task

FULL LOAD only

FULL LOAD tasks are probably the simplest form of a Qlik Replicate task. With a Full Load only task, the data will be copied from the source tables to the target tables (Base Tables) and then the task will stop.

The target tables are basically a mirror image of the source tables with static data based on the last time the task was run.

The target tables are not kept in sync. This type of configuration is very similar to an old-style ETL type job, where the data is copied over one time when the task runs.

This Full Load type of task can be scheduled to run using replicates built-in scheduler or the Qlik replicate command line or rest API.

The task and target tables can utilize some features of Qlik replicate such as transformations and filters.

NOTE: A full load-only task can get around a limitation with LOB columns that are in a table with no primary key.
This limitation is for CDC tasks and the following is the CDC task notification you will get:

Column 'MyLob' was removed from table definition 'dbo.No_PK_LOB': the column data type is LOB and the table has no primary key or unique index

It is required that a table with LOBs has a primary key, due to the way the task will perform a lookup back to the source table to get the LOB value. As this lookup is only done during the CDC phase, it is not a limitation for a Full Load task, which will be able to read the entire LOB column when it is copying the source data to the target table.

Full Load settings screen:

CDC only

CDC only tasks will capture changes from the source and write them out to the target database. In this type of task, there are typically no (Base Tables) in the target.

The Apply changes setting is typically disabled and only the Store Changes setting is enabled. With this type of configuration, the task will read changes from the source and write out the records to the Qlik Replicate Store Changes table also known as __CT tables.

This type of task configuration is typically used when the data in the target __CT table is going to feed a downstream process. The structure of these __CT tables is usually based on the source table and will contain the fields from the source as well as any transformation fields. The big feature of the __CT table is that it also contains the various header information from the source such as commit time, Operation Indicator etc.

Store Changes settings screen:

FULL LOAD and CDC task

FULL LOAD and CDC tasks will typically contain the target (Base Tables) and they will populate those tables during the full load phase of a task.

Then the CDC phase of the task will capture every change to the source records and apply them to the target (Base Tables). This is a very typical configuration for a Qlik replicate task.

Note: this type of task can also have the store changes enabled (as described above in 2)

Conceptual vs. Actual task process order

Clarification of an often misunderstood task phase order related to the Full Load and CDC task:

When discussing Full Load and CDC combined in a single task, we think in terms of the Full Load phase starting first and then the CDC phase starting second to apply changes and keep the task in sync. While this is conceptually correct, the phases actually are reversed and in fact, the CDC phase is the one that starts first; capturing and caching changes.

Once the CDC phase starts, then the full load phase will start.

This order is needed in order to insure that any changes made to the table during the Full Load will be captured.

For example, if you happen to have a very large table that takes three hours to fully load and the CDC phase did not start until it was complete, you would miss those three hours of changes being applied to the table.

If you have ever seen a message in the log at the top of the log about consistency timeout this is why:

W: Transaction consistency timeout occurred. x transactions are still open

CDC - Apply changes setting screen:

Related Content

Transformation: Source - Filter for Delete
Filter for last 90 days of data in Qlik Replicate
Qlik Replicate Transaction Consistency Timeout occurred. xtransactions are still open
Qlik Replicate Full Load and CDC Split Task: Considerations

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.

Environment

Qlik Replicate 

Talend Studio periodically requires patch updates. In an air-gapped environment with no internet access, Talend Studio cannot reach the default update site (https://update.talend.com/Studio/8/updates/latest) to download and apply patches automatically.

This article describes how to download a Studio patch on a machine with internet access, then apply it locally by pointing Talend Studio's update settings to the downloaded patch file.

1. Download the required Talend Studio patch on a machine with internet access, and save it to a folder on the local machine, for example: D:/Talend_Patch/Patch_20260619_R2026-06_v1-8.0.1.zip 
   For information on how to download the patch, see How to download Qlik Talend Product patches.
2. Configure Talend Studio to use the local patch in Talend Studio:
   1. go to Window > Preferences > Talend > Update Settings.
   2. Change the Update URL field from the default update site https://update.talend.com/Studio/8/updates/latestto the local patch path, for example: jar:file:/D:/Talend_Patch/Patch_20260619_R2026-06_v1-8.0.1.zip!/
   3. Click Apply and Close.
3. Open Feature Manager in Talend Studio, and follow the prompts to complete the local patch installation

Environment

• Talend Studio

The IBM DB2 for iSeries source endpoint occasionally encounters an error during the CDC stage. This issue appears to be linked to the presence of the IBM i Access ODBC Driver versions 7.1.26 and 7.1.27.

The error message in the task log file:

[SOURCE_CAPTURE ]E: Error parsing [1020109] (db2i_endpoint_capture.c:652)

The issue specifically arises during the CDC stage; however, the Full Load stage operates smoothly without any complications.

Resolution:

Qlik has certified the DB2i ODBC driver version 07.01.029. An update to the official Qlik documentation is currently pending.

Either:

• Upgrade your IBM i Access ODBC client to 07.01.029, 
• or downgrade from versions 07.01.027/07.01.026 to 07.01.025

For compatibility reasons, it's advisable to revert to version '07.01.025' if you choose to downgrade, as '07.01.026' exhibits the same issue.

Various factors can contribute to encountering the 'Error parsing' message, including:
    • DB2i ODBC Version '07.01.027' (as described in this article)
    • In a single task, the total number of captured tables exceeds 300
    • The source table is created by DDS
    • Garbage data in table
    • Special characters in table object identifier (table name, or column name)
If you continue to encounter the error after switching to '07.01.025', please reach out to Qlik Support for further assistance.

Cause:

The behavior of the IBM DB2i ODBC Versions '07.01.026' & '07.01.027' differ slightly from that of '07.01.025'. In certain scenarios, it may return incorrect column lengths

Internal Investigation ID(s):

#00158029, #00160002, QB-26413

Environment:

• Qlik Replicate All versions
• IBM DB2i All versions
• IBM DB2i Client versions '07.01.026' and '07.01.027'

Qlik Replicate 

When the Qlik Sense Capability Service Logs takes up a huge amount of disk space you have the possibility to clean the logs and to prevent them from growing as big as they were again.

Resolution

You can clean out the folder using the methods described in How To Reduce Log Folder Size Over Time.

After the folder has been cleaned out there is the possibility to switch off the Capacity Service logging:

1. Open the services.conf in C:\Program Files\Qlik\Sense\ServiceDispatcher and add the line --log-level=off under the capabilityservice.parameters section.
   
   [capabilityservice.parameters]
   --port=${CapabilityPort}
   --file="${PWD}\..\CapabilityService\capabilities.json"
   --log-level=off
   
   

   The parameter can be one of the following:

   • info (default) 
   • warning
   • error
   • off
   
   
   
2. Save the services.conf
3. Restart the Qlik Sense Service Dispatcher Service

Cause

Logs in the folder C:\ProgramData\Qlik\Sense\Log\CapabilityService are not automatically archived in the Qlik Sense archived logs folder.

Environment

Qlik Sense Enterprise on Windows February 2019 and above

For Qlik Sense Enterprise for Business (Cloud), see Loading of an app is hanging when using Qlik Cloud.

Working in a Qlik Sense app after remaining inactive causes fails with the error: 

Connection to the Qlik Sense engine failed for unspecified reasons. Refresh your browser or contact our system administrator

The issue specifically affects external users who have been inactive until a network device's (Firewall, Router, etc.) idle timeout was reached. This is followed by a connection reset for the TCP WebSocket session.

Cause:

TCP WebSocket connection is terminated by the firewall because the firewall is not receiving any TCP traffic such as keep-alive packets from client browser (e.g. Firefox, older Chrome versions).  Specific web browsers have their own tcp keep-alive behavior. 

This issue may be found with less frequency with IE because it sends the TCP Websocket keep-alive more frequent than any other main stream browser. Here are the default intervals for the three main browsers latest releases as of September 2020:

Default TCP-Keep-Alive intervals:

• Chrome: 45 sec
• Edge: 45 sec
• Internet Explorer: 30 sec (see IE: Change Keep-Alive timeout)
• FireFox 81.0: 10sec for ~2 minutes (115sec) period, then a keep-alive packet every 10 minutes

General Information

This functionality is by default switched off not to affect any existing customers. Customers who do not experience any issues with web sockets terminated by the network due to inactive SHOULD NOT switch this feature ON since it will send unnecessary traffic on the network. See How are WebSockets used in QlikSense ? for more information.

How to configure?

1. Stop the Qlik Sense Proxy Service
2. Edit the file C:\Program Files\Qlik\Sense\Proxy\Proxy.exe.config This location may not be available if Qlik Sense was not installed in the default location.
3. Add the configuration key:
   

   <add key="WebSocketPingInterval" value="0"/>   <!-- Interval in seconds for the web socket ping to the client (a value of "0" is disabling the ping)–>

   Where value is a suitable positive number depending on the inactive web socket timeout setting in the network. The effective interval that the Qlik Sense Proxy server will send keep-alive messages towards the client my oscillate between 2 x value and 1 x value, since it also takes into account backend inter-process socket activity. Eg: setting the value of WebSocketPingInterval to 30 may lead to keep-alive messages sent to the client every 30 or 60 seconds.
   
   Note: The Qlik Sense Proxy service may not send keep-alive packets if it detects activity on that client's Websocket tcp session.
   
   Recommended is 60-300 second range, shorter interval generates more load on Proxy CPU and network. It should be set as high as possible, meaning it's best to identify at which interval an intermediate proxy cuts the connection when it perceives it as idle, and then set the ping interval to a slightly smaller value.
   
   A too small number (e.g. less than 30) will load the proxy and the network and IS NOT recommended. Suitable numbers could be 60 to 300 (i.e. 1 minute to 5 minutes), but it all depends on the network configuration (if the network removes web sockets that have been inactive for more than 5 minutes then, of course, the value must be set something less than 5 minutes (i.e. less than 300)). If a lower value is required, it is recommended to investigate the components involved in the connection, such as third party proxies and network load balancers to configure them with less restrictive timeouts. 
   
   It is possible that the same WebSocketPingInterval value has different behaviors in each Qlik Sense Hub section due to third party network device. The value may keep the connection live in Dashboardbut, but still lose connection in Data Load Editor. You may test with a lower WebSocketPingInterval value until the proper value is found to keep connection in all sections. For example, when connectingCloudFlare as web application firewall, theWebSocketPingInterval value may need to set to 10 seconds otherwise "connection lost" may still be received in Data Load Editor even the rest of Qlik Sense Hub keeps connected.
   
   
4. Restart the Qlik Sense Proxy Service.

Related content:

• Hub access times out with: Error Connection lost. Make sure that Qlik Sense is running properly  
• How are WebSockets used in QlikSense ?
• Loading of an app is hanging when using QlikSense Cloud
• Browser Timeout
• Qlik Sense HUB timeout even with session timeouts configured correctly
• Increase session timeout in QlikSense

The max concurrent reloads can be configured in the Qlik Sense Management Console.

1. Open the Qlik Sense Management Console
2. Navigate to Schedulers 
3. Enable the Advanced section (if not already on by default)
4. Set the required max concurrent reloads
   
   
   

    

IMPORTANT TO REMEMBER

• A reload node can run NumberOfCores - 2 
  
  This means: If your reload node has 8 CPU Cores, it can run 6 concurrent reloads at its maximum.
  
  Use the guideline (NumberOfCPUCores - 2) when performing capacity planning on the possible amount of concurrent scheduled reloads.
  
  
• The cores can be physical cores or virtual cores; any CPU cores Qlik Sense can "see".
  
  
• While a reload task typically consumes one core, this is not a hard rule. It can require multiple cores.
  
  
• Allowing more parallel reloads than CPU cores available does not improve the runtime of concurrent tasks. The reload node's resources will deplete. 
  
  This also means: With more parallel reloads than cores the probability for total starvation increases since the QIX engine is CPU hungry and other processes (for example, the operating system) might not get enough CPU cycles to perform their duties.
  
  
• Each running reload is loaded into RAM. This means that the average RAM footprint grows with more parallel reloads.
  
  
• Qlik Sense will queue scheduled reloads when system resources reach their threshold 
  
  
• To validate that environment needs proper capacity planning, go to C:\ProgramData\Qlik\Sense\Log\Scheduler\Trace\<Server>_System_Scheduler.txt, an example log shows below:
  
  

  <ServerName>_System_Scheduler.txt
  Domain\qvservice    Engine connection released. 5 of 4 used 
  Domain\qvservice    Engine connection 6 of 4 established 
  Domain\qvservice    Request for engine-connection dequeued. Total in queue: 25

Concurrent settings

Use the "Max concurrent reloads" to limit the maximal concurrent tasks can be run at same time on current node. By default, it's set to 4, which means only 4 tasks can be run at same time on this node.

When the 5th task comes in:

1. It will be queued by sequence. 
2. The queue has a time setting, which will eliminate (erase) a queued task if the timeout limit reaches. By default, it's set to 30 mins, in this case, if none of the first 4 tasks finishes in 30 minutes after the 5th task comes in, then the 5th task will be cancelled due to timeout. It has to be triggered again (manually or next scheduled time slot).
3. Once one of the 4 running tasks finishes, the 5th task will be executed on this node if it's not timed out.
4. If you set timeout to 0, this will make the queue never timeout.
5. It's suggested not to run more than 10 concurrent reloads at once, unless the schedular node has an extreme amount of resources dedicated to it.
6. If there is low memory or cores available on the node, then some tasks may kick off however take several hours to complete. Adding resources to the node running the reloads is suggested.

Multi-node deployment

On a multi-node deployment, tasks will be balanced from the manager node to any node(s) designated as workers.

It's highly advised to check if the central node configured is set to Manager and Worker or Manager. When set to Manager, it will send all reload jobs to the reload/scheduler nodes, as it should. However if a central node is set to Manager and Worker, this means the Central node will also be involved in performing reloads. This is not recommended. 

The work flow looks as follows:

1. Manager node receives a new task execution request.
2. Manager node checks the resource availability on each of the worker nodes. 
3. Manager node assigns this task to the node with the lowest number of running tasks per "Max concurrent reloads" setting.

The improvement to track the Max concurrent reloads can, if desired, be disabled. This reverts Sense to an older load balancing method that relies only on CPU usage. 

To disable the setting:

1. Open the Scheduler.exe.config, which by default is located in: C:\Program Files\Qlik\Sense\Scheduler\Scheduler.exe.config
2. Set DisableLegacyLoadBalancingBehavior setting to false
3. Restart Qlik Sense Scheduler Service
4. Repeat these actions on each node of the cluster running the Qlik Sense Scheduler Service

Example

In our example, we allow one concurrent reload, but we assume that two reloads are executed at the same time.

• If Task A is executed first, Task B is queued.
• If Task A is executed first and then fails, Task B is executed after the failure.
• After Task A's failure, Task A is queued and will execute after Task B has finished.

When executing a Talend Job that writes data to an Excel file, the Job may generate repeated warnings similar to:

[WARN ] 08:39:14 org.apache.http.client.protocol.ResponseProcessCookies -
Invalid cookie header: "set-cookie: activate_ca_modal_triggered="";
Expires=Thu, 01 Jan 1970 00:00:10 GMT; Path=/".
Invalid 'expires' attribute: Thu, 01 Jan 1970 00:00:10 GMT

The same Job may execute without these warnings when the output component is changed to tFileOutputDelimited.

In most cases, this message is generated by Apache HttpClient while processing an HTTP response cookie. It is a warning from the HTTP client cookie parser and is not, by itself, evidence that the Excel output operation has failed.

Talend's tFileOutputExcel component writes Excel files as part of the File component family.

Resolution

Because the warning is cosmetic, the recommended approach is to suppress the specific logger.

1. In Talend Studio, navigate to File > Edit Project Properties.
2. Go to Log4j (or Log4j2, depending on your Studio version).
3. Add the following XML configuration snippet inside the <Loggers> section of your log4j2.xml (or log4j.xml) template:
   
   XML
   
   

   <!-- Suppress Apache HttpClient cookie parser warnings -->
   <Logger name="org.apache.http.client.protocol.ResponseProcessCookies" level="ERROR" additivity="false">
       <AppenderRef ref="Console"/>
   </Logger>
   <Logger name="org.apache.http" level="ERROR" additivity="false">
       <AppenderRef ref="Console"/>
   </Logger>

   
   
4. Click Apply and Close to save the project settings.
5. Re-run the job locally in Studio or redeploy the job artifact to your Remote Engine / Job Server.
6. Confirm that the ResponseProcessCookies warning no longer appears in the console output.

Cause

The warning originates from Apache HttpClient, used internally by Talend and related libraries such as Apache POI or components that perform HTTP-related operations.

During Excel output processing, a library initialization or background request can receive a Set-Cookie header that uses an Expires value in the past (Thu, 01 Jan 1970...). This is a standard technique to delete a cookie. Apache HttpClient’s default cookie specification is strict about date formatting and logs a WARN-level message when it cannot parse the attribute according to its expected rules.

The delimited-file path does not trigger the same library behavior or HTTP interaction, so the warning does not appear. The message is purely informational and does not affect data integrity, job success, or the generated Excel file.

Environment

• Talend Studio

A Talend job scheduled to run every day at the same time fails because Talend Management Console (TMC) detects that the same plan already has an execution in Pending or Running status.

This occurs when the plan is configured to disallow overlapping executions. The Talend Management Console prevents the new execution from starting while the previous execution is still active.

Resolution

If concurrent executions are safe and intended for the job:

1. Open Talend Management Console.
2. Navigate to the affected plan.
3. Open the plan's Details page and click Edit.
4. Open the Schedule section.
5. Enable Allow parallel run of this plan.
6. Save the plan configuration.

If parallel execution is not appropriate, keep the option disabled and review the schedule and execution duration. As a best practice, leave at least a one-minute margin between the expected completion of one execution and the start of the next scheduled execution.

Also verify whether any previous executions are unnecessarily remaining in Pending status and investigate the underlying job or Remote Engine capacity if applicable.

For additional information, see Talend Management Console – Scheduling plans.

Cause

The scheduled plan does not allow parallel executions, and the previous execution has not completed when the next scheduled trigger occurs.

This can happen when:

• The job execution takes longer than expected.
• A previous execution remains in Pending or Running status.
• The schedule interval does not provide sufficient time for the previous execution to finish.

Environment

• Talend Cloud
• Talend Management Console

Testing the PostgreSQL Source Endpoint in Qlik Replicate may fail with the following error:

Failed to load Postgres driver. Cannot load libpq.dll

Resolution

You should have two entries in the system environment variables pointing to the following folders (default locations):

• C:\Program Files\PostgreSQL\12\bin
• C:\Program Files\psqlODBC\1202\bin

Both folders must include the libpq.dll file.

If the connection test fails even with libpq.dll present in both directories, then:

1. Copy the libpq.dll file from odbc\bin (C:\Program Files\psqlODBC\1202\bin) to  ~\Replicate\bin 
2. Restart the Qlik Replicate server service and the Replicate UI server service

Environment

• Qlik Replicate

After upgrading Qlik Compose from 2022.5 to 2023.11 or 2024.12, attempting to generate and run the Data Mart job fails with the following error:

SQL compilation error: invalid identifier "MASTER_CONSIGNMENTLEG_MASTER_CONSIGNMENT_GLOBI_consignment_INVOICE_GLOBI_relations_OID" 

Resolution

To resolve, change the "is_pk" property from false to true for the OID columns in the Aggregate Fact definition.

For new Data Mart jobs, the OID column defaults to true. This issue only affects older Aggregate Facts that include dimensions.

Detailed steps:

1. Create a deployment package of the project where the issue exists.
2. Extract the ZIP file and open the JSON file.
3. Locate the Aggregate Fact table definition in the JSON file that has the issue. For example: FACT_GLOBI_AGG_FINANCIAL_PLAN_NON_FIN_REP.
   
   
   
   
4. Locate the _OID columns within the Aggregate Fact definition.
   For example, FACT_GLOBI_AGG_FINANCIAL_PLAN_NON_FIN_REP contains four OID columns:
   • S_sec_department_id_GLOBI_department_GLOBI_department_OID
   • S_invoice_relation_id_GLOBI_relations_GLOBI_relations_OID
   • S_sec_branch_id_GLOBI_branchGLOBI_branch_OID
   • S_sec_branch_id_GLOBI_relation_address_GLOBI_branch_OID
5. For each _OID column, check the value of the "is_pk" property.
6. If "is_pk" is set to false for any _OID column, update it to true.
7. Save the changes, then re-ZIP the JSON file along with the readme.txt file.
8. Deploy the updated ZIP file into the existing project.
9. Regenerate the statements for the Data Mart.
10. Run the Datamart ETL job.

Environment

• Qlik Compose

The CICD publishing phase may fail with the following error:

org.talend.ci:cloudpublisher-maven-plugin:8.0.13:publish (default) on project <project>: Get the latest published version failed

This article identifies the two most common root causes and their solutions:

Get the latest published version failed: Unauthorized
Caused by: jakarta.ws.rs.NotAuthorizedException: HTTP 401 Unauthorized

Get the latest published version failed: Not Found
Caused by: jakarta.ws.rs.NotFoundException: HTTP 404 Not Found

Identify which root cause applies to you by reviewing the log stack.

Resolution

Unauthorized

This indicates an invalid Talend Management Console (TMC) token and may require a review of what TMC region is currently in use.

Resolution

• Validate the TMC token. If unsuccessful, create a new token to use.
• Verify the TMC region: Storing your global variables in Jenkins 

Not Found

Not Found points to an incorrect TMC URL.

Resolution

• Review the TMC URL currently configured as per Storing your global variables in Jenkins 

Internal Investigation ID(s)

00470337, 00470122

Environment

• Talend Data Integration

When SMTP is used to send outgoing mail and the legacy DigiCert G1 SSL cert provided by Microsoft to Qlik is still in use, emails sent from Qlik Cloud will fail. 
 

Resolution

The SMTP endpoint must present a chain anchored to a currently trusted DigiCert root (for example: Global Root G2, with the correct intermediate), supported by DigiCert and already used by modern Microsoft/O365 endpoints.
 

Cause

Qlik Cloud does not support the legacy DigiCert Global Root CA (G1), which was dropped from the SMTP bundle due to security concerns (see Review the G1 root removal advisory | docs.digicert.com).

This blocks the use of a locally issued certificate when the endpoint relies on G1.

Internal Investigation ID(s)

SUPPORT-10911

Environment

• Qlik Cloud

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

Requirements

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

Core Documentation

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

Qlik Sense Content Monitor User Guide

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

  • Use Case: 

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

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

  • See the attached Qlik Sense Content Monitor User Guide

Configuration Guide

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

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

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

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

    • A "Troubleshooting" section.

  • Use Case:

    • New installations.

    • Troubleshootings.

    • Tuning performance for long reloads.

  • See the attached Qlik Sense Content Monitor Configuration Guide

Environment

• Qlik Sense Enterprise on Windows

Some versions of Qlik Sense Desktop show a significant delay when opening the hub after authenticating through Qlik Cloud.

Affected versions

• Qlik Sense Desktop November 2025 SR 1
• Qlik Sense Desktop May 2026 IR

Resolution

A fix to QCB-35278 is expected in August 2026. 

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 for updates on ID QCB-35278.

Cause

Defect QCB-35278 is caused by the Qlik Cloud backend introducing a delay during the login process.

Internal Investigation ID(s)

QCB-35278, SUPPORT-10476