With an RDBMS target endpoint such as Oracle, where Change Processing Mode is set to Batch optimized apply and both Apply Changes and Store Changes are enabled, paired INSERT and DELETE operations may be merged during batching.

This results in no change being applied to the target.

In Batch Optimized Apply mode, Qlik Replicate commits changes in batches. Before applying these batches, Qlik Replicate performs preprocessing to group transactions as efficiently as possible. Events sharing the same primary key (or RRN) may be merged as follows:

In more detail:

Batch optimized apply mode, Qlik Replicate merges INSERT/DELETE pairs so that the net result is “no-op” at the target. However:

• These operations are still fully recorded in the Store Changes tables
• They also appear in the GUI → Applied Changes view
• This sometimes leads users to believe that operations (e.g., a DELETE) were “lost,” but this behavior is expected and designed into Batch optimized apply

To avoid merge-related side effects during sensitive processing windows, temporarily switch the task to Transactional apply.
Transactional apply enforces the exact sequence of operations.

Once the critical period has passed and the task has stabilized, you can safely switch back to Batch optimized apply to maintain performance.

Scenarios and Workarounds

Below are two scenarios outlining how this behavior appears in practice, as well as workarounds.

Scenario One: Stop Task and Restart from Timestamp

1. Create a task with full load, apply changes, and store changes enabled.
2. Start the task and let Replicate create the target table.
3. Insert one row into the source at 10:00 AM → both source and target now contain one row.
4. Stop the task.
5. Delete the row from the source.
6. Restart the task from 10:00 AM (or slightly earlier).
   (Current time is 10:10 AM)

Observed Behavior

One row remains in the target even though it was deleted in the source. All changes, however, are correctly recorded in the store changes tables.

Workaround

Before step 6, switch the task to Transactional apply. After changes up to step 4 are applied, switch back to Batch optimized apply.

Scenario Two: Stop Task and Resume

1. Stop a CDC task. Assume both source and target are empty.
2. Insert one row into the source.
3. Run a Full Load only task → both source and target now have one row.
4. Delete the row in the source.
5. Resume the CDC task.

Observed Behavior

One row remains in the target. All changes are still correctly logged in the store changes tables.

Workaround

Before step 5, switch to Transactional apply. After the changes from step 3 are applied, switch back to Batch optimized apply.

Notes

• During the Transactional apply period, some INSERT events may be captured more than once. Duplicate rows will be discarded by the target primary key
• If the target table has no primary key, duplicate rows may need to be removed manually
• Setting the target endpoint to UPSERT mode may help reduce duplicates
• Some endpoints (e.g., Snowflake) do not support Transactional apply. In such cases, a reload may be required

Environment

• Qlik Replicate

While processing CDC for update events, the following warning may be shown:

[ASSERTION       ]W:  'UPDATE (3)' event of table 'XXXXXX' with id '41975' does not contain all key values, stream position '00000000.6086b294.00000001.0065.02.0000:7857.1110812.16'  (streamcomponent.c:2991)

[ASSERTION       ]W:  Please use the ASSERTION logger in the verbose mode to log all possible problematic events of all captured tables  (streamcomponent.c:2992)

 [TASK_MANAGER    ]W:  Table 'XXXXX' (subtask 0 thread 1) is suspended. Performing 'update' operations in "Transactional apply" mode is not supported by Databricks Delta  (replicationtask.c:3239)

Resolution

Enable supplemental logging on Oracle.

Cause

Supplemental logging is not enabled on the Oracle source database.

With supplemental logging disabled, Oracle does not include the full primary key or before-image key columns in the redo/CDC logs for UPDATE events. 

As a result:

• Replicate received UPDATE events without all required key values
• The missing key values triggered the ASSERTION warning

Since the row cannot be located on the target, Qlik Replicate attempts to apply an UPDATE to Databricks Delta. Delta does not support UPDATE operations in Transactional Apply mode, which caused the table to be suspended.

Environment

• Qlik Replicate

On September 9, 2025, Bitbucket disabled the creation of new App Passwords. Atlassian now recommends using API Tokens for authentication with external tools. Previously, Talend Studio users could connect to Bitbucket using App Passwords associated with their Atlassian accounts. However, as of September 9, 2025, creating new App Passwords is no longer possible, and Bitbucket has suggested using API Tokens instead.

Creating a Bitbucket API Token

1. Sign in to your Bitbucket Cloud account. Choose the Settings icon next to the username at the top right and choose "Atlassian Account Settings".
2. Go to "Atlassian Account settings" → "Security" tab in the top and "API Tokens" section.
3. Click "Create and manage API tokens".
4. Select "Create API token with scopes".
5. Give your token a name.
6. Select "Bitbucket" radio button.
7. Select the required scopes
   
   For Talend Studio to authenticate and access repositories, make sure to enable the necessary scopes:
8. Click "Next" and select "Create Token", then copy the token.
   
   Store it securely — Bitbucket will not show it again.

Configuring Talend Studio Connection

1. Launch Talend Studio and choose the Cloud connection.
2. Choose the project connected to Bitbucket.
3. Enter your Bitbucket username (not email) and the API Token as the password.
4. Ensure that the Bitbucket repository URL is correct (For instance, https://bitbucket.org/<workspace>/<repo>.git).
5. Test the connection.
6. If the token has the correct scopes, the connection will be successful.

Environment

• Talend Data Integration 
• Talend Studio 

After installation of Qlik Sense you get HTTP Error 502.4 - Bad Gateway when opening QMC or Hub and might see the following error message in your browser:

Environment:

Qlik Sense Enterprise on Windows 
 

The error message is displayed by the Microsoft Internet Information Service (IIS) which is already installed on the host you are trying to install Qlik Sense. As Qlik Sense comes with it's own webserver it might conflict with other web servers already installed on the same host. 

Resolution:

Uninstall Microsoft Internet Information Service (IIS) on the host you install Qlik Sense with the following steps:
 

1. Click Start, click Run, type Appwiz.cpl, and then click OK
2. In the Add/Remove Programs window, click Add/Remove Windows Components
3. In the Components box of the Windows Components Wizard, click to unselect the Internet Information Services (IIS) check box
4. To complete the uninstallation, click Finish, and then Close

When an On-Demand App Generation (ODAG) link is created in a selection app and the app is transferred to another owner, then the new owner can only see the option "Add to App Navigation" in the right-click context menu. Options "Edit" and "Delete" are missing. 

The same issue happens when the selection app is duplicated by another user.

Resolution:

This is a known limitation of Qlik Sense and has been reported in defectQLIK-83203.

There are default security rules: CreateOdagLinks and ReadOdagLinks.
But no default rule for Update/ Delete of ODAG links.

 

A work-around solution at the moment is to create custom security rules that grants Update/ Delete access of ODAG links to the new app owner, similar to the followings:



ODAG links are meant to be managed similar to Data connections, where a connection created in one app can be used in other apps. However, while the QMC provides a Data connections tab to list down all connections and control related ownership/ permissions, such management GUI is not available for ODAG links. R&D is considering the ODAG link management page in future releases of the product.

If the upgrade to a new version of Qlik Talend Data Catalog fails (For example: Talend Data Catalog 8.0 to Talend Data Catalog 8.1), the errors show as below in the system log:

    [-1/initDb] 2024-11-29 17:25:24 MIRWEB_E0007 Operation Migrate Data Mapping to Metamodel failed see (Manage > Operations for details) 　

   [-1/initDb] 2024-11-29 17:25:24 MIRWEB_S0006 Skipping operation: Migrate Diagrams to Metamodel 

   [-1/initDb] 2024-11-29 17:25:24 MIRWEB_S0006 Skipping operation: Delete Documentable Models 　

   [-1/initDb] 2024-11-29 17:25:24 MIRWEB_S0006 Skipping operation: Migrate Join Relationships to Metamodel 　

   [-1/initDb] 2024-11-29 17:25:24 MIRWEB_F0003 Service initialization error: Contact your System Administrator.

Resolution

To prevent issues (like corrupted data) from happening during migration process, please be sure to:

• Set up Solr, the database, and replace the folders before starting the new Talend Data Catalog application server.
• Do not touch or execute any other processes that may affect Talend Data Catalog while the auto migration takes place (especially do not restart the Talend Data Catalog application during the process). Wait until it completes before doing anything else. 

As a review, please double check all migration steps outlined in the following documentation: Upgrade Process |Qlik Talend Help.

If any other processes that could affect Talend Data Catalog is done at the same time or if the Talend Data Catalog applications are restarted during the migration process, problems can arise, which may potentially require you to start over the upgrade process.

Cause

The errors identified above have resulted from the migration steps not being executed correctly. 

Environment

#Talend Data Catalog

Talend Data Integration 

"RestConnectorMasterTable" General Script Error in statement handling

RestConnectorMasterTable:
20200826T102106.344+0000 0088 SQL SELECT
20200826T102106.344+0000 0089 "name",
20200826T102106.344+0000 0090 "value"
20200826T102106.344+0000 0091 FROM JSON (wrap off) "contactCustomData"
20200826T102106.344+0000 0092 WITH CONNECTION (
20200826T102106.344+0000 0093 URL "      ",
20200826T102106.344+0000 0094 HTTPHEADER "Authorization" "**Token removed for security purpose**"
20200826T102106.344+0000 0095 )
20200826T102106.967+0000 General Script Error in statement handling
20200826T102106.982+0000 Execution Failed
20200826T102106.986+0000 Execution finished.

Environment

Qlik Sense Enterprise on Windows 

Resolution

To be able to catch the exact error and mitigate the issue they need to apply our recommended best practices for error handling in Qlik scripting using the Error variables
Error variables 
Script control statements 

Set to ErrorMode=0 it will ignore any errors and continue with the script. You can use the IF statement to retry the connection or move to another connection for a few attempts and then it will change it to ErrorMode=1 and fail or just disconnect on its own.

A sample script is located here, but further options can be added from the Help links already provided.
Qlik-Sense-fail-and-retry-connection-sample-script 

Note: QlikView scripting is the same in these functions for Qlik Sense unless otherwise stated, but there are some very helpful items in the links.
Best-Practice-Error-Handling-in-Script 

Cause 

Error with the fetch of the token with the rest call. If the number of rows in a table doesn't match or is less than expected, trigger the script to throw an error and have it try to load the table again for more records, or if the count is off, do a Loop until returns the correct number.

Internal Investigation ID(s) 

QB-3164

The Talend Cloud Management Console Public API enables users to manage Talend Management Console (TMC) from an external system (for example, a scheduler, script, or program).

Environment

This article uses Talend Cloud API 1.2, which supports operations for tasks, plans, and promotions in Talend Cloud. Note: Talend Cloud API 1.1 only supports operations on tasks, and version 1.0 has been deprecated.

Content:

• Prerequisites
• Executables and executions
• Generating a token
• API operations for tasks in Talend Cloud
• Get available Tasks - /executables
• Get Task details - /executables/{id}
• Execute Task - /executions
• Terminate Task execution - /executions/{id}
• Get Task execution status - /executions/{id}
• API operations for plans in Talend Cloud
• Get available Plans - /executables/plans
• Get Plan details - /executables/plans/{id}
• Execute Plan - /executions/plans
• Get Plan execution status - /executions/plans/{id}
• API operations for promotions in Talend Cloud
• Get available Promotions - /executables/promotions
• Get Promotion details - /executables/promotions/{id}
• Execute Promotion - /executions/promotions
• Get Promotion execution status - /executions/promotions/{id}
• Conclusion

Prerequisites

• Talend Cloud subscription
• Talend Cloud Management Console access credentials (can also be used to access API)

Executables and executions

A list of supported operations is available on the API documentation page. There are three URLs, each for a different region of Talend Cloud. However, the list of operations does not vary by region.

• US: https://api.us.cloud.talend.com/tmc/

• EU: https://api.eu.cloud.talend.com/tmc/

• APAC: https://api.ap.cloud.talend.com/tmc/

The API operations consist of executables and executions, with a separate set of operations available for each.

• Operations related to executables use the GET method to get information about executables, such as tasks, plans, and promotions.
• Operations related to executions perform actions such as execute or terminate using the POST, DELETE, or GET method.
• Supported operations on executables get lists of tasks, plans, or promotions, as well as details for these by ID, for instance, using "Get task details by task ID".
• The POST method is used for an operation that supports execution of a task, plan, or promotion.
• The DELETE method is used for deleting a task.

Generating a token

The first step in using the API is generating a personal access token; then you can start managing TMC through the API. Follow the detailed steps for Generating a personal access token in the Talend Help Center. You get a token that looks like this:

As mentioned in the help, you can use this token for authorization, for example in a curl command:

curl -X GET 'https://api.us.cloud.talend.com/tmc/v1.2/executables' \
-H 'Authorization: Bearer eyJraWQiOiJpYW0tb2lpYy1jbG91ZCIsImQu2WembcCB'

This article references the Swagger UI available as part of API documentation authorization; it uses email and password login credentials instead of a token.

API operations for tasks in Talend Cloud

Here are the operations available for accessing a task or its details, and for managing task execution:

Here are details on how to perform each operation with different scenarios:

Get available Tasks - /executables

/executables lists available tasks in all environments using the GET method.

The HTTPS URL for this operation is https://api.eu.cloud.talend.com/tmc/v1.2/executables.

To try this in the Swagger UI:

1. Click the name of the operation to expand it.
2. Click the Try it out! button.

Notice that /executables is highlighted in the Curl and Request URL sections:

The Response Body section lists all tasks in all environments of the Talend Cloud subscription. In this operation, a Response Code of 200 indicates that the API call is successful.

Get Task details - /executables/{id}

To get task details by task ID instead of getting all tasks, you use the /executables/{id} operation. The HTTPS URL for this operation is https://api.eu.cloud.talend.com/tmc/v1.2/executables/5c275067e91341357ef0b86b.

Execute Task - /executions

To execute a task, use /executions and specify the execution ID. In the example below, the parameter required for execution is the executable ID. In this case, the task is executable. Specify the parameter in JSON format. The response is the execution ID.

You can verify the execution logs in TMC by opening the task and viewing the run history. The execution ID returned as part of Response Body is used to find the execution. The screenshot shows the log for the sample task execution:

Terminate Task execution - /executions/{id}

To terminate a task in execution, use /executions/{id} called using the DELETE method. For example, in the Swagger UI as below, using the f88b8a8f-4a51-4ac5-9453-2c8eaf1e01a4 execution ID returned as part of a previous request (in the Execute Task example) terminates task execution. Because task execution in the previous API call was successful, the response returned for this terminate operation is Nothing to do for the task: its status is EXECUTION_SUCCESS.

In a real-world scenario, the terminate task would help stop execution of any long-running task.

Get Task execution status - /executions/{id}

Before terminating a task, calling /executions/{id} using the GET method returns the status of the task. This operation of getting the execution status by ID tells you whether the task is in progress, has been completed, or has failed. In the screenshot below, for the f88b8a8f-4a51-4ac5-9453-2c8eaf1e01a4 sample execution ID, notice the detailed status returned by the operation as part of Response Body:

API operations for plans in Talend Cloud

Get available Plans - /executables/plans

Like tasks, the cloud API allows you to manage plans externally. A plan is the step-by-step execution of one or more tasks. To list all plans created in all environments, the request URL, submitted using the GET method, is https://api.eu.cloud.talend.com/tmc/v1.2/executables/plans. Response Body lists plans in JSON format:

Get Plan details - /executables/plans/{id}

To get details on a particular plan using the executable ID, the request URL, submitted using a GET method, is https://api.eu.cloud.talend.com/tmc/v1.2/executables/plans/{id}. In this example, the executable ID is 49fe0c6d-95e8-413c-aa97-13a15e506350, so the request URL is https://api.eu.cloud.talend.com/tmc/v1.2/executables/plans/49fe0c6d-95e8-413c-aa97-13a15e506350.

The response for this operation consists of detailed plan information in JSON format:

Execute Plan - /executions/plans

To execute a plan from an external system, the request URL format is https://api.eu.cloud.talend.com/tmc/v1.2/executions/plans. This URL is submitted using the POST method. The parameter required for this operation consists of an executable ID in JSON format:

Just as with a task execution using the POST method, a plan execution returns an execution ID as the response. A plan execution generates logs for every task in the steps in the plan:

Get Plan execution status - /executions/plans/{id}

To get the execution status of a plan, the request URL format is https://api.eu.cloud.talend.com/tmc/v1.2/executions/plans/{id}. For this example, the request URL is https://api.eu.cloud.talend.com/tmc/v1.2/executions/plans/67975122-8e92-4b81-8818-6ce161763ece.

Response Body contains detailed information about the plan execution:

API operations for promotions in Talend Cloud

Get available Promotions - /executables/promotions

To get a list of all promotions, the request URL is https://api.eu.cloud.talend.com/tmc/v1.2/executables/promotions. Whether it is a list of promotions, tasks, or plans, the API call returns the response based on the credentials or token permissions (based on user access). This screenshot shows the sample get available promotions operation:

Get Promotion details - /executables/promotions/{id}

You can get the details of a promotion from the executable ID. Notice the highlighted Request URL and Response Body sections:

Execute Promotion - /executions/promotions

For the execute promotion operation, the request URL is https://api.eu.cloud.talend.com/tmc/v1.2/executions/promotions, called using a POST method that requires a JSON parameter:

{
 "executable": "5ce39250b0daaa43cfc64271",
 "keepTargetResources": true,
 "advanced": {
   "artifactId": "5d5bc62796184c43f45d310e",
   "artifactType": "ACTION"
 }
}

The value for artifactType in the JSON parameter determines the scope of the promotion. Refer to Managing promotions in the Talend Help Center for details about promoting artifacts, tasks, plans, workspaces, and environments.

The ACTION value promotes an artifact.

You are ready to explore the execute promotion operation in more detail. For the promotion in this article, the source environment is Vpdev and the target environment is VPProd. An artifact is promoted using artifact ID 5d5bc62796184c43f45d310e in the VPdev environment:

The target environment does not have this artifact before executing the promotion:

When you execute the promotion, Response Body for the execute promotion operation contains the execution ID:

The artifact has been promoted:

Get Promotion execution status - /executions/promotions/{id}

Using the execution ID returned as the response with the previous execute promotion operation, you can obtain the execution status of another operation, Get Promotion execution status. The request URL format is https://api.eu.cloud.talend.com/tmc/v1.2/executions/promotions/{id}. For example, the URL for the execution ID in the previous operation is https://api.eu.cloud.talend.com/tmc/v1.2/executions/promotions/5d5c0223780a65440e3fed53:

Conclusion

You have learned how to use the Talend Cloud Management Console Public API to manage tasks, plans, and promotions from an external system. You can use either a personal access token or Talend Cloud access credentials. The best practice is to use a personal access token to manage Talend Cloud tasks, plans, and promotions. Performing a combination of operations through the API is ideal for most use cases that require external management.

When a Talend DI OSGI service using tRestRequest/tRestResponse component skips certain JARs during packaging, those libraries are not compiled into the service-name.jar/lib directory, causing the service to fail at runtime due to missing dependencies.

How can the missing JARs be included in the service package without requiring additional bundle installations to load them?

How To

By default, studio\plugins\org.talend.repository_8.0.2.20xxxxxx_xxx.jar/resources/osgi-exclude.properties has the default list of exclude jars.

Let's use tSendMail component as example: jakarta.mail-api*.jar 

You can remove it

1. Close Talend Studio.
2. If <studio>/esb/osgi-exclude.properties  does not exist, copy
   plugins/org.talend.repository_8.0.2.*.jar/resources/osgi-exclude.properties into <studio>/esb/ directory.
3. Open the file, delete the single line
   

   jakarta.mail-api

4. Restart Studio and rebuild job

The user should not introduce conflicting jar files, since Talend Runtime container provides its own jar files.
In addition to that, if newer versions of jar files are packaged into another Route to be deployed, due to the Runtime shares jar files across all deployments, it may also be a point of conflict.

Environment

• Talend ESB 
• Talend Studio 

How To Grant Users The Access To Data Model Viewer.

With default security rules and settings, users can not see the data model for published apps. However, we can achieve this by creating/updating security rules through the Qlik Sense Management Console.

Resolution

Option 1: Create a new Security Rule

1. Go to the Qlik Sense Management Console
2. Open Security Rules
3. Click Create new 
4. Create the following rule:
   1. Name = DataModelViewers
   2. Description = A description of your choice.
   3. Resource filter = App_*
   4. Actions = "Read","Update"
   5. Conditions = Users of your choice or a previously defined role you will tag the users with.
   6. Context = Both in hub and QMC or Only in hub
      
5. Click Apply

Option 2: Tagging users as ContentAdmins

This requires a rework of the ContentAdmin rule and will provide far more permissions to users than Option 1. See ContentAdmin for details on what a ContentAdmin is allowed to do. 

1. Tag the users you want to be able to see data models with the ContentAdmin role. 
2. Go to the Security Rules 
3. Locate the default ContentAdmin rule and open it
4. Modify the rule by changing QMC only to Both in hub and QMC
5. Click Apply

Cannot install or launch the Qlik Web Connector standalone package (January 2024 and higher versions) on Microsoft Windows 2016 and 2019 servers. 

The installation or launch fails with:

QlikWebConnectors.exe - This application could not be started.

This application requires one of the following versions of the .NET Framework:
.NETFramework,Version=v4.8.1

Resolution

A Qlik Web Connector configuration file change is needed to force the use of .NET Framework 4.8 with the Qlik Web Connector standalone package.

1. Navigate to the Qlik Web Connector extraction folder; example: C:\QlikWebConnectorsJuly2025
2. Find and edit the following two files:
   • QlikWebConnectors.exe.config
   • QlikWebConnectorsSVc.exe.config
3. In each file, find and update the following line by changing v4.8.1 to v4.8:
   

   <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.8.1" />

   to
   

   <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.8" />

Cause

The Qlik WebConnector standalone package requires Microsoft .NET Framework 4.8.1. See System requirements for Qlik Web Connectors.

However, Microsoft .NET Framework 4.8.1 is not supported on Windows 2016 and 2019 servers. For more information, refer to Compatible operating systems | learn.microsoft.com. Windows 2016 and 2019 servers support .NET Framework 4.8 or lower. 

Environment

• Qlik Web Connectors

Attempting to connect to Gmail SMTP server over port 587, Amazon SES over port 587 and Office Mail 365 over port 587 using SSL, results in a connection error.  This article explains what needs to be done in order to make this connection work properly.

Environment:

• QlikView all versions

Cause:

Email servers may require encryption when sending email.

Resolution:

Use the following steps to configure an SSL connection to an SMTP email service when using Publisher:

1. Browse to C:\Program Files\QlikView\Management Service and edit the QVManagementService.exe.config file.
2. Look for string "UseSSLForSMTP". If the entry already exists, edit its value to "true"
3. If "UseSSLForSMTP" does not exist, place the following two lines of code under the <!--****** SMTP ****** --> section:
   • <!--The following allows SSL connections to an SMTP mail service-->
   • <add key="UseSSLForSMTP" value="true"/>
4. Browse to C:\Program Files\QlikView\Distribution Service and edit the QVDistributionService.exe.config file.
5. Look for string "UseSSLForSMTP". If the entry already exists, edit its value to "true"
6. If "UseSSLForSMTP" does not exist, place the following two lines of code under the <!--****** SMTP ****** --> section:
   • <!--The following allows SSL connections to an SMTP mail service-->
   • <add key="UseSSLForSMTP" value="true"/>

For Gmail, use port 587(smtp.gmail.com);Also the Gmail account needs to:

• "2-Step Verification": Disabled;
• "Access for less secure apps": Enabled
• Change the above settings from https://www.google.com/settings/security

For Amazon Simple Email Service(SES), use port 587.

For Microsoft 365 service, use smtp.office365.com for address and port 587. Also see the following article for an alternative: Office 365 SMTP setup for Qlikview

At Qonections 2018 I hosted a session called "Top 10 Qlik GeoAnalytics Tricks". Here's the app I used with all tips including test data.

The app covers the following:

1. Test location lookup
2. Custom popups
3. Icon layer
4. Sense chart in popup
5. Area outline custom width
6. Store icons in app
7. Custom labels
8. Multi line labels
9. Dynamic SVG symbols
10. Points to lines
11. Shared segments in routes
12. Drill downs
13. Custom map background color
14. Reducing coordinates
15. Show unselected on map
16. Node graphs with map
17. Override conversion in the connector
18. Buffer using Travelarea and closest
19. Multi Language support

The app is updated with QS Nov 2019, most of the tips works with prior versions too.

If you liked it, here's more tips in the same style:

• Qlik GeoAnalytics tips 2019 Qonnections
• Qlik GeoAnalytics tips 2020 QlikWorld
  

Similar but for Visualizations in general:

• Sense Visualization tips 2021 part V QlikWorld
• Sense Visualization tips 2020 part IV
• Sense Visualization tips 2020 Qlik World, part III
• Sense Visualization tips 2019, part II
• Sense Visualization tips 2019 Qonnections, part I

A Qlik Replicate task with a SAP Hana trigger-based endpoint in CTS mode has an hour of latency for its source endpoint with a log stream task. 

SAP Hana Source Advanced Tab for the trigger-based endpoint:

Resolution

This latency is expected with tasks that include a high volume of tables (example: a task with three SAP applications with more than 2000 tables).

With trigger-based endpoints, part of the CDC process involves reading the incoming changes from the attrep_cdc_changes_cts table to be processed in all tables present in the task.

Only one CDC thread per task is available in a trigger-based endpoint, regardless of whether it is a log stream task or a direct task reading from the SAP Hana Source. 

This is due to the fact that when processing changes from a trigger-based endpoint, Qlik Replicate reads the changes from the table and processes them via a SQL OUTER Join on the SAP Hana Source of the underlying Table(s). 

The more tables, the more latency is expected. 

If you need more than one CDC thread, split the task into multiple tasks and tables to gain added CDC threads rather than the default one per task.

Environment

• Qlik Replicate

Following an upgrade to Qlik Sense Enterprise on Windows November 2025 Initial Release, Qlik  NPrinting On-Demand reports fail with this error message:

On-Demand reporting control is not supported in this environment

The issue occurs with any supported web browser and persists after recreating the On-Demand button within the Qlik Sense app.

Resolution

The problem is being investigated as defect SUPPORT-7229.

We suggest delaying the Qlik Sense November 2025 Initial Release upgrade if Qlik NPrinting On-Demand is in use.

Internal Investigation ID(s)

SUPPORT-7229

Environment

• Qlik Sense Enterprise on Windows November 2025 IR
• Qlik NPrinting