This article answers the most frequently asked questions about Qlik Discovery Agent. It is split into five sub-sections:

• General FAQ
• Availability and Integration
• How does Discovery Agent work?
• Technical FAQ
• Insight Generation Logic

If you are looking for information on how to get started, check out the Discovery Agent Interactive Walkthrough and our Discovery Agent Documentation.

General FAQ

What is Qlik Discovery Agent?

Discovery Agent is an AI-powered, always-on monitoring capability in Qlik Cloud that automatically detects meaningful changes, anomalies, and trends in your data. It requires no rules, thresholds, or manual setup. Discovery Agent identifies spikes, drops, trend shifts, baseline changes, and data quality issues, then delivers clear, plain-language insights in a prioritized feed.

What makes Discovery Agent different from traditional alerting?

Traditional BI alerts rely on predefined thresholds or manual logic. Discovery Agent uses the Qlik Analytics Engine and its associative capabilities to evaluate wide combinations of data relationships automatically and proactively surface only those insights that matter. It is context aware, adaptive, and far more scalable than rules driven systems.

Who is Discovery Agent for?

• Executives who want high-level visibility into what changed
• Business users who need easy-to-read insights without deep analytics skills
• Non-technical users who do not want to build dashboards or rules
• Analysts who want automated detection to replace repetitive KPI monitoring

Availability and Integration

Does Discovery Agent work with Qlik Cloud Analytics?

Yes. Discovery Agent is built directly into Qlik Cloud Analytics and leverages the Qlik Analytics Engine for associative, large scale anomaly detection.

A Premium or Enterprise subscription is required. See Qlik Pricing for details or contact your Qlik account representative. 

Does Discovery Agent integrate with Qlik Answers?

Yes. You can ask questions directly from an insight card, and context from the insight will be transferred into Qlik Answers.

Is Discovery Agent available on Qlik Sense Enterprise Client-Managed?

No. Discovery Agent is built exclusively for Qlik Cloud.

Does Discovery Agent impact app performance?

No. Monitoring runs outside active dashboards, ensuring no performance impact on live analytics experiences.

Does Discovery Agent follow Qlik Cloud security and governance rules?

Yes. Insight delivery respects user permissions, governed access, and security boundaries.

How does Discovery Agent work?

How does Discovery Agent detect insights?

Discovery Agent analyzes updated app data models using associative evaluation to identify:

• Spikes or dips
• Trend shifts
• New or emerging baselines
• Record highs and lows
• Values above or below expected patterns
• Missing or inconsistent data

No rules or thresholds are required.

Is Discovery Agent real-time?

Discovery Agent is always on, but processes changes when the application’s data model updates. Insights refresh after reload and appear in the feed once the system evaluates new data. Updated are currently capped at one reload per day.

How often does the feed refresh?

The feed automatically refreshes upon reload. For most apps, this occurs once per day or whenever new data is introduced.

Can I customize the insights I see?

Yes. You can follow specific apps or insight categories once the Following tab is released. Filtering options are also planned to help tailor results.

Technical FAQ

What are Insight Triggers?

Insight Triggers are structured metric definitions that serve as the foundation for generating analytical insights within the application. Each trigger is composed of a measure or expression,  such as a calculated field or KPI, along with a set of additional configuration parameters. These parameters include the frequency at which the trigger evaluates data and the type of calculation to be applied (example: sum, average, count).

Together, these elements define the conditions under which an insight is surfaced to the user.

Do I Have to Set a Date Period for Each Trigger?

Yes, a date period is required for every trigger you configure.

All insights generated by the system are trend-based, meaning they analyze data over time to identify patterns, changes, or anomalies. This requires a date period to be added to the trigger's associated group. Without a defined time range, the system cannot perform the temporal comparisons necessary to produce meaningful insights.

How Do I Refresh the Insight Feed?

The Insight Feed refreshes automatically each time the page is reloaded. No manual refresh action is required. The feed itself is regenerated once per day, and this regeneration is triggered by the introduction of new data into the application or applications that contain active triggers. As a result, the feed will always reflect the most recent data available as of the last daily reload cycle.

Can I Filter Individual Values in a Dimension?

Filtering functionality is available in the Feed. A Filter button is currently visible at the top of the feed during the preview phase of the application. Users can use this to find specific insights in the feed.

How Many Triggers Can I Create?

• Each application supports a maximum of 50 triggers. For each trigger that has been configured, the system will calculate and present up to 5 insights per reload cycle.
• A tenant-wide guardrail exists to help control the volume of insights in the feed, providing broad analytical coverage across your defined metrics and expressions.

Where Are Triggers Stored?

Triggers are stored directly within the application in which they are created. They are not stored externally or in a centralized repository. That means each application manages its own set of triggers independently, and triggers defined in one application will not carry over to or affect another application.

Can I Ask Questions Directly in the Feed?

Direct question-and-answer functionality within the feed is available.

The Insight Feed is integrated with Qlik Answers, enabling users to ask natural language questions without leaving the feed interface. Because each card displayed in the feed is tied to a specific application, context from the relevant card will be automatically transferred to Qlik Answers to ensure accurate, contextually appropriate responses.

Why Am I Seeing a Large Number of Old Insights?

This behavior is expected and occurs specifically after the first reload following the creation of new triggers.

During this initial reload, the system performs a comprehensive scan of all available historical data, rather than only the most recent data. This allows it to identify any and all qualifying insights across the full dataset. This is a one-time process. All subsequent reloads after this initial one will only evaluate and surface insights based on newly introduced data, so the volume of older insights will not continue to grow with each reload.

Does This Feature Require the Cross-Region Inference Toggle?

Yes. The Insight Feed and its associated trigger functionality require the cross-region inference toggle to be enabled. Please ensure this setting is activated in your environment before attempting to configure triggers or access the feed. If you are unsure how to enable the cross-region inference toggle, contact your system administrator or refer to the relevant configuration documentation.

How Do I Remove Insights from the Feed?

To remove specific insights from the Insight Feed, you must delete the trigger that is generating those insights. Because the feed is dynamically generated based on active triggers, removing a trigger will prevent its associated insights from appearing in future feed reloads.

Deleting a trigger is a permanent action.

If you wish to stop surfacing certain insights temporarily, consider whether disabling or modifying the trigger may be a more appropriate course of action, depending on your platform's available options.

Does This Feature Support Section Access?

Section Access is not currently supported for applications used with the Insight Feed.

Any application that has Section Access enabled is incompatible with this feature at this time. As a result, all users who have been granted access to a given application will be able to see the insights generated from that application's triggers, regardless of any Section Access restrictions that may otherwise apply within that application.

This is an important consideration when deciding which applications to configure with triggers, particularly for datasets that contain sensitive or role-restricted data. Support for Section Access may be introduced in a future release.

Insight Generation Logic

How many data points are required to generate an insight?

Below is the minimum data requirement:

Weekly/Monthly/Quarterly/Yearly aggregation

• Spike detection, record high/low, model deviation: 4–50 data points
• Trend/baseline change: 20–50 data points

Daily aggregation

• Spike detection, record high/low, model deviation: 7–365 data points
• Trend/baseline change: 20–365 data points

Why am I not getting any insights?

Missing dates in the date field may prevent calculations. Creating a master calendar in the
load script can resolve this. Qlik is exploring options for date imputation.

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

When only a Unique Index Key is defined in the source, the task will by default create a non-clustered key in the target.

This article documents how to create a Primary Key in the target by introducing an Internal Parameter at the SQL Server target. 

Resolution

Source: Oracle
Target: SQL Server

Add the following parameter:

• $info.query_syntax.create_index  
• Value: ALTER TABLE ${QO}${TABLE_OWNER}${QC}.${QO}${TABLE_NAME}${QC} ADD CONSTRAINT ${QO}PK_${TABLE_NAME}${QC} PRIMARY KEY ( ${COLUMN_LIST} ) 

Make sure columns with a unique index defined at the source, as well as columns that are marked as Key Manually in the UI, have the NOT NULL constraint enabled.

Environment

• Qlik Cloud
• Talend Cloud

QTAC-2537 R2026-08 patch introduced a label sorting issue in the Talend Job Conductor.

Sorting the label on the Execution Plan page in previous patches works as expected. The issue is specific to sorting label names in the Job Conductor, whereas sorting the label name in ascending or descending order fails. 

Resolution

This issue will be fixed in an upcoming Talend Administration Center patch. If a solution is required as soon as possible, another alternative is to revert to a previous patch, as this only impacts version QTAC-2537 (R2026-08).

Review the Talend Release Notes for details.

Internal Investigation ID(s)

QTAC-2707

Environment

• Talend Administration Center

Jobs show significantly degraded performance when running on a Dynamic Engine compared to executing on a Remote Engine.

Environment:

• Talend Cloud

Resolution

On a Dynamic Engine, the job runs inside a pod, i.e., a container. This container has its own operating system and libraries, separate from the host node. Because of this, it is sometimes necessary to add Java options at job launch (for example, on a run profile in the Talend Management Console) to allocate more resources to the job inside the container.

There are two main options to add, depending on the root cause of the problem:

Large data volume processing (memory-bound)

This is typically a memory issue. Add the following options:

1. Kubernetes-specific:

   • -XX:MaxRAMPercentage= sets the maximum JVM heap size as a percentage of the memory allocated to the container (similar to Xmx).
     
     

2. Talend-specific, at the container level (not the job itself):

   • -K8S:PodRAMRequest=
   • -K8S:PodRAMLimit=
     
     

   These set the memory usage for the pod itself.

Complex data processing (CPU-bound)

When the processing logic itself is complex, it is preferable to adjust the CPU allocation instead. By default, a job is limited to 30% of the Kubernetes node's CPU. This limit exists mainly to prevent a single job from completely freezing the node.

This limit can be raised with the following options, which allocate more CPU to the pod:

• -K8S:PodCPURequest specifies the initial CPU allocation for the pod.
• -K8S:PodCPULimit sets an upper limit on the pod's CPU usage, preventing it from monopolizing CPU resources.

Examples:

• -K8S:PodCPURequest=0.5: request to use 50% of node CPU for the job
• -K8S:PodCPULimit=1: can use up to 100% of node CPU
• -XX:MaxRAMPercentage=50: allocate 50% of pod RAM for the job heap size

Cause

The default CPU usage is 0.3, as defined in the Dynamic Engine's env file. This value is set to prevent any node CPU overhead.

Joint customers of Qlik and Alation were dancing for joy the minute they realized that there was Qlik Application Automation Connector for their Alation Cloud Catalog. 

If reading that phrase was difficult for you, it's ok. It took me a dozen takes trying to say it when I recorded the video you will find below. Powerful, but such a tongue twister. 🤣

Connecting

Like with any of the Qlik Application Automation connectors, to get started you will need to drag any of the many many many blocks to your canvas. 

Then you will need to establish the connection parameters. Simply provide the name you wan to use for your connection, your login credentials for your Alation Cloud Catalog tenant and lastly your "instance_name." Please notice below you DO NOT want to input the entire instance, just your specific company name that is part of the full name. 

Use Case

Considering the fact that I had to scroll for 10 seconds just to make the GIF file above showing the many blocks I suppose I better narrow the use case for the rest of this post down for you ... the main block that I wanted to show you was the brand spanking new block "Add Object to BI Server."

The use case that block was built to support was any scenario where you wanted to build your own user defined hierarchy within Alation. So I chose a use case that affords us the perfect opportunity to do just that ... We will be exporting all of the METADATA about my applications to my Alation Cloud Catalog. [Notice I didn't say saving our applications or sharing our data. I'm just talking about the metadata that describes our applications.]

Spaces --> Applications --> Sheets --> Objects

Thus the goal at the end is to have a folder in your Alation Cloud Catalog for each of your spaces, and inside a list of each of your applications that are part of that space, and inside that a list of each of your sheets that are part of that application, and inside of that a list of all of your objects that are part of that sheet. 

I have attached a copy of the Qlik Application Automation project/workspace for you "SendSpaceToAlation.json". So if you want to feel free to upload the workspace into a new Qlik Application Automation and you can follow along.

One thing you will notice in the project, and in the accompanying video, is that I intentionally put two Conditional blocks in my Qlik Application Automation: One that checks for a particular Space name and only goes through the process for it, and a second that checks if the Sheets are public or not. It's always good practice to limit what you are doing so that it's easier to validate everything in an isolated fashion. Once you get it working you can simply drag everything from the Yes condition of the space out, remove the condition and then output all of your spaces. Likewise, if you wish to catalog all of the metadata from your personal sheets in the application feel free to do that. Understand, that they are YOUR personal sheets, not everyone else's.

BI Server

The blocks that I utilize as part of this automation, "Add Folder to BI Server", "Add Object to BI Server", both require you as their names suggest to identify your target BI Server.  If I was just building the attached project for myself then perhaps I would utilize Qlik Application Automation's ability to simply select my BI Server from a lookup: 

If you have ever watched my You Tube series on Qlik Application Automation you will know I'm kidding. I don't like having to worry about maintenance so I typically make everything a variable. Especially when it is something like the Alation Cloud Connector Server ID that I will use multiple times throughout the project. Which works out well for you because that means when you get a .JSON project from me, like the one attached, all you need to do is modify a few variables and you are up and running. 

If you don't know the Server ID to use you have 3 options:

1. Go ahead and choose it 1 time from the lookup and it will give you the ID

2. If you are in your Alation Cloud the Server ID will be listed in the URL path

3. You could swap out the blocks to use the small "List BI Servers" block I left in this project for you. It provides you the same list that shows up if you use the Lookup functionality.

Sleep

My lack of sleep is none of your concern. However, you do need to be aware of the importance of "sleep" when it comes to the Alation Cloud Connector API's. You see they are Asynchronous. Meaning they don't make you wait while they are off and doing their thing, they return control to you immediately so you can multi-task. That is normally a great thing, but in this case we have an issue. I can't add Applications to a Space that doesn't exist yet. I can't add Sheets to an Application that doesn't exist yet. I can't add Objects to a Sheet that doesn't exist yet. 

Hence, the need for sleep. Not for you or I, but for the automation. So you will see several blocks within the project set to sleep for X number of seconds after calling the Alation Cloud Connector API's. As I point out in the video depending on your environment you may need to adjust those wait times. 

Seeing is Believing

Now that I have laid the ground work for what the use case and the special situations we are dealing with here is a video that will walk you through the project and let you see what the outcome would be in your Alation Cloud tenant. 

Above and Beyond

Hopefully, I have provided enough information in text/video to get the attached template working in your environment. But that's really just the beginning. If you listened carefully I showed an alternative template where I created a folder called Sheets under the Application, then put all of the Sheets in it. Perhaps your next step is to make that work as well.

The most important thing about that suggestion was to leave room for other folders under the Applications like "Master Dimensions", "Master Measures" and "Master Visualizations." How cool would that be? 

While I could have handed you a project template that did that for you, the most important reason I post content or share content is for YOUR LEARNING. I aim to provide enough to get you comfortable/confident working with new things like this Qlik Application Automation Connector for your Alation Cloud Catalog. 

Whether you succeed or fail at the challenge, please feel free to share below. After all, that is what Qlik Community is all about. 

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.

This article is currently under review.

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

The article also includes

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

Scenario

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

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

The data model

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

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

The Write Table

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

The Write Table is then extended with three editable columns:

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

Prerequisites

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

Steps

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

   
   

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

    

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

    

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

      

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

     

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

     

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

     

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

     

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

     

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

     

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

     

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

     

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

       

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

Environment

• Qlik Cloud Analytics

This article explains how to retrieve data using Qlik Sense Analytics (on-premises and Cloud) from SAP OData services, taking into account the 2026 SAP security patches.

Background

An SAP security patch released in June 2026 technically blocks third-party use of the ODP framework over RFC (SAP Note 3255746). This is the interface most dedicated SAP connectors used. Only ODP via RFC is affected, not RFC in general, and SAP names ODP via OData as the compliant fallback for data access outside SAP systems. A time-limited revert option exists but expires in December 2026 (SAP Note 3731818).

Only Qlik's SAP ODP connector (Qlik Cloud) is affected. Depending on the access level you have in your SAP environment, you can also use our SAP connectors to extract data from SAP NetWeaver SAP connectors in Qlik Sense Client Managed, Qlik Cloud and QlikView (these are not affected by SAP restrictions).

But if data extraction only relies on OData services, Qlik's OData connector or REST connector are the only alternative.

Requirements

What is needed on the SAP side (macro level):

• AP Gateway as the OData layer. Every OData service is served by SAP Gateway (NetWeaver Gateway), either embedded in the ABAP system or as a separate hub. In S/4HANA, it's built in. This is the component that turns backend objects into OData endpoints.
• Service activation. A service must be registered and activated in /IWFND/MAINT_SERVICE (plus the underlying ICF node in SICF). SAP ships thousands of standard services inactive by default. Activation per service is a deliberate admin step, not automatic.
• A user and authorizations. A dedicated communication/service user with S_SERVICE for the endpoint plus the application-level authorizations for the data behind it. Gateway auth doesn't bypass application auth — if the user can't see the plant in SAP, the OData service won't return it either.
• Network and authentication. HTTPS with a trusted certificate and an auth method. The consumer supports:
  • Basic Auth (the simple on-prem case)
  • OAuth2/SAML for cloud scenarios
    In S/4HANA Cloud (public edition), the connection runs through communication scenarios/arrangements rather than manual Gateway configuration. For Qlik Cloud Analytics reaching an on-prem Gateway, either the endpoint is reachable from the cloud, or you go through Qlik Data Gateway – Direct Access.
• For ODP-based services, additionally, the Operational Delta Queue (ODQ) must be active, and the source object must be released for ODP extraction. Delta then works via the OData subscription/delta-link mechanism backed by ODQ.

What can be exposed as OData

Two families

Family A: ODP-based OData services. SAP Gateway can generate an OData service on
top of the ODP framework, and then the answer is essentially yes — anything ODP
supports:

• DataSources/Extractors. SAPI context: the classic 2LIS_* logistics extractors, FI
  extractors, etc., released via RSA5
• ABAP CDS views annotated with @Analytics.dataExtraction.enabled: true (ABAP_CDS
  context), delta-capable when the change-data annotations are set
• BW/BW4HANA InfoProviders. BW context
• SLT-based table replication. SLT context
• HANA information views

These services are generated in the Gateway Service Builder (SEGW) via the ODP-
extraction wizard. They support full load plus genuine delta — the extractor's delta logic
is preserved and exposed through OData delta tokens.

Family B: regular (non-ODP) OData services. Anything the ABAP stack can model:

• A CDS view with @odata.publish: true (one annotation, auto-generated service)
• Hand-built services in SEGW (mapping DDIC tables, CDS as reference data source,
  BAPIs/RFCs, or custom code)
• RAP service bindings (OData V2/V4). The modern S/4HANA way
• The standard APIs delivered from the SAP Business Accelerator Hub

These have no delta mechanism by default. Incremental loads are your problem as the
consumer. Typically $filter on a change date or timestamp field, which only works if the
underlying object carries one reliably.

Limitation with the generic OData connector in Qlik Sense Client Managed

The generic OData connector speaks plain OData, which is fine for Family B and for full loads only from Family A. (delta load can only be managed with a REST connector).

OData is a chatty protocol. While paging, $select to trim width, and gzip help, nobody should plan a nightly full load of BSEG-scale tables over it.

Options to retrieve data from SAP ODATA services

In Qlik Cloud Analytics

• How to connect to data from SAP OData services and retrieve data with Qlik Cloud Analytics REST connector

In Qlik Sense Enterprise on Windows

• How to connect to data from SAP OData services and retrieve data with Qlik Sense Enterprise on Windows REST connector
• How to connect to data from SAP OData services and retrieve data with Qlik Sense Enterprise on Windows ODATA connector

Environment

• Qlik Cloud
• Qlik Sense Enterprise on Windows
• QlikView

This article explains how to connect to data from SAP OData services and retrieve data with the Qlik Sense Enterprise on Windows ODATA connector.

Requirements

• A valid SAP account to access the ODATA services in the SAP environment
• (Optional) A certificate installed on the Qlik Sense Enterprise on Windows server if you communicate with the ODATA services through SSL

Configuration

1. Create a new application in your Qlik Sense workspace, and go to the Data Load editor
2. On the right panel, click New Connection and choose the ODATA connector
3. Configure the connection:
   1. Enter the URL of the SAP ODATA service and your credentials
   2. Test the connection, then click Save
      
      

How to retrieve and load data

1. Identify the entities (resources) of the ODATA service
   1. On the data connection you created, click the Data button
      
      
      
      
   2. On the left menu, choose ListResources (A) and enter $format=xml (B) in the OData Query Options, then choose application/atom+xml in Accept (C) and click Preview data (D)
      
      
      
      
      
      
   3. Retrieve the list of entities
      
      
   4. Check and click GetData, then enter the following parameters:
      • The name of the entity from which you want to retrieve data in OData Resource Path
      • $format=xml in OData Query Options
      • Application/atom+xml in Accept
        
        
        
        
   5. Click Preview data
      
      
   6. Click on Insert script
      
      
      
      
      
      
2. The next step is to curate the load statement and optionally provide business-friendly names for the SAP fields.
   
   Example:
   
   
   
   
3. Repeat all steps for each entity you want to retrieve data from. Then curate the load script to avoid synthetic keys and build a functional data model in your analytic application.

The example in this article is provided as is and only documents a basic option. Further customization can be achieved using a data architecture with QVD layers.

Optional: Instead of manually going through all the steps, it is possible to use an LLM and a skill on SAP and Qlik to generate a first curated version of the full load script by providing the LLM the metadata file of the OData service. It would save some time in the building process.

Environment

• Qlik Sense Enterprise on Windows

This article explains how to connect to data from SAP OData services and retrieve data with the Qlik Sense Enterprise on Windows REST connector.

Requirements

• A valid SAP account to access the ODATA services in the SAP environment
• Optional: A certificate installed on the Qlik Sense Enterprise on Windows server if you communicate with the ODATA services through SSL

Configuration

1. Create a new application in your Qlik Sense workspace, and go to the Data Load editor
2. On the right panel, click New Connection and choose the REST connector
3. Configure the connection:
   1. Enter the URL of the SAP ODATA service
      
      
      
      
   2. Choose Basic Authentication and enter your credentials
      
      
      
      
   3. Under Query parameters, add sap_client and enter its value; do the same for $format, then check Allow “WITH CONNECTION”
      
      
      
      
   4. Test the connection, then click Save

How to retrieve and load data

1. Identify the entities (resources) of the ODATA service
   1. On the data connection you created, click the Data button
      
      
      
      
   2. Expand the left menu and choose EntitySets
      
      
      
      
   3. Retrieve an Entity from the list, edit the connection again, and paste the Entity at the end of the URL
      
      
      
      
   4. Test and save the connection
      
      
   5. Expand the left menu and tick results:
      
      
      
      
   6. Click on Insert script
      
      
      
      
2. The next step is to curate the load statement by adding the WITH CONNECTION statement and defining variables for the SAP environment used in the connection.
   
   Example:
   
   
   
   (Optional) Followed by providing business-friendly names for the SAP fields.
   
   Example:
   
   
   
   
   
3. Repeat all steps for each entity you want to retrieve data from. Then curate the load script to avoid synthetic keys and build a functional data model in your analytic application.

The example in this article is provided as is and only documents a basic option. Further customization can be achieved using a data architecture with QVD layers.

Optional: Instead of manually going through all the steps, it is possible to use an LLM and a skill on SAP and Qlik to generate a first curated version of the full load script by providing the LLM the metadata file of the OData service. It would save some time in the building process.

Environment

• Qlik Sense Enterprise on Windows

This article explains how to connect to data from SAP OData services and retrieve data with the Qlik Cloud Analytics REST connector.

Requirements

• A valid SAP account to access the ODATA services in the SAP environment
• A functional Qlik Data Gateway Direct Access
• The SAP OData generic URL added in the gateway settings under the REST connector; the URLs are case-sensitive
  
  
  
  
• Optional: A certificate installed on the Qlik Sense Client Managed server if you communicate with the ODATA services through SSL

Configuration

1. Create a new application in your Qlik Sense workspace, and go to the Data Load editor
2. On the right panel, click New Connection and choose the REST connector
3. Configure the connection:
   1. Choose the data gateway and enter the URL of the SAP ODATA service; do not forget the forward slash (/) at the end of the URL
      
      
      
      
   2. Choose Basic Authentication and enter your credentials
      
      
      
      
   3. Under Query parameters, add sap_client and enter its value; do the same for $format, then check Allow “WITH CONNECTION”
      
      
      
      
   4. Test the connection, then click Save

How to retrieve and load data

1. Identify the entities (resources) of the ODATA service
   1. On the data connection you created, click the Data button
      
      
      
      
   2. Select JSON as Response type and expand the left menu, then choose EntitySets
      
      
      
      
   3. Retrieve an Entity from the list, edit the connection again, and paste the Entity at the end of the URL
      
      
      
      
   4. Test and save the connection
      
      
   5. Expand the left menu and check results:
      
      
      
      
   6. Click on Insert script
      
      
      
      
2. The next step is to curate the load statement by adding the WITH CONNECTION statement and defining variables for the SAP environment used in the connection.
   
   Example:
   
   
   
   (Optional) Followed by providing business-friendly names for the SAP fields.
   
   Example:
   
   
   
   
   
3. Repeat all steps for each entity you want to retrieve data from. Then curate the load script to avoid synthetic keys and build a functional data model in your analytic application.

The example in this article is provided as is and only documents a basic option. Further customization can be achieved using a data architecture with QVD layers.

Optional: Instead of manually going through all the steps, it is possible to use an LLM and a skill on SAP and Qlik to generate a first curated version of the full load script by providing the LLM the metadata file of the OData service. It would save some time in the building process.

Environment

• Qlik Cloud Analytics

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

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

When running a silent installation, Qlik Sense is installed without dialog prompts. This means all features, properties, and user selections are set before performing a silent installation. All setup options available in the installer user interface can be performed with silent operators.

For details, see:

• Performing a silent installation
• Performing a silent upgrade

The installation can be broken down into three steps.

Step 1: Prepare the installation in accordance with the Qlik Sense system requirements

1. Set up a shared folder. 
2. Ensure the folder is shared with the service account.
3. The service account should be a local administrator.

Step 2: Prepare the configuration file 

This file will be used in the next step and includes all remaining configuration settings. This must be configured for the installation to complete successfully. See Shared persistence configuration file syntax (choose your respective version).

We have attached an example file. You'll need to change 'xxx' to the shared folder network path. Please consider using a hostname or DNS name instead of localhost. 

Step 3: Execute the silent installation

Run CMD as an administrator, then provide the installation command with the required arguments. When building the command, do not forget to confirm that you have read the EULA with the argument accepteula(1|0). Customer agreements can be found at Legal Agreements.

Example script to execute a silent install:

Qlik_Sense_setup.exe [-silent] {-log "path\filename"} {layout="path"} {accepteula=1|0}{desktopshortcut=1|0} {skipstartservices=1|0} {installdir="path"} {userwithdomain="domain\user"} {userpassword="password} {dbpassword="password"} {hostname="www.machinename.domain.com"} {sharedpersistenceconfig="configfilepath"} {senddata=1|0} {skipvalidation=1|0} {databasedumpfile="path"}

Environment

This template was updated on December 4th, 2025 to replace the original installer and API key rotator with a new, unified deployer automation. Please disable or delete any existing installers, and create a new automation, picking the Qlik Cloud monitoring app deployer template from the App installers category.

Installing, upgrading, and managing the Qlik Cloud Monitoring Apps has just gotten a whole lot easier! With a single Qlik Automate template, you can now install and update the apps on a schedule with a set-and-forget installer using an out-of-the-box Qlik Automate template. It can also handle API key rotation required for the data connection, ensuring the data connection is always operational.

Some monitoring apps are designed for specific Qlik Cloud subscription types. Refer to the compatibility matrix within the Qlik Cloud Monitoring Apps repository.

'Qlik Cloud Monitoring Apps deployer' template overview

This automation template is a set-and-forget template for managing the Qlik Cloud Monitoring Applications, including but not limited to the App Analyzer, Entitlement Analyzer, Reload Analyzer, and Access Evaluator applications. Leverage this automation template to quickly and easily install and update these or a subset of these applications with all their dependencies. The applications themselves are community-supported; and, they are provided through Qlik's Open-Source Software (OSS) GitHub and thus are subject to Qlik's open-source guidelines and policies.

For more information, refer to the GitHub repository.

Features

• Can install/upgrade all or select apps.
• Can create or leverage existing spaces.
• Programmatically verified prerequisite settings, roles, and entitlements, notifying the user during the process if changes in configuration are required, and why.
• Installs latest versions of specified applications from Qlik’s OSS GitHub.
• Creates required API key.
• Creates required analytics data connection.
• Creates a daily reload schedule.
• Reload applications post-install.
• Tags apps appropriately to track which are installed and their respective versions.
• Supports both user and capacity-based subscriptions.

Requirements

The user running the automation needs to have:

• API permission; see Permission settings — Features and actions | help.qlik.com.
• The tenant admin role; see Permissions granted by security roles | help.qlik.com.
• The audit admin role (when deploying the Answers Analyzer application); see Permissions granted by security roles | help.qlik.com.

Configuration

Update just the configuration area to define how the automation runs, then test run, and set it on a weekly or monthly schedule as desired.

Configure the run mode of the template using 7 variable blocks

Users should review the following variables:

1. configuredMonitoringApps: contains the list of the monitoring applications which will be installed and maintained. Delete any applications not required before running (default: all apps listed).
2. refreshConnectorCredentials: determines whether the monitoring application REST connection and associated API key will be regenerated every run (default: true).
3. reloadNow: determines whether apps are reloaded immediately following updates (default: true).
4. reloadScheduleHour: determines at which hour of the day the apps reload at for the daily schedule in UTC timezone (default: 06)
5. sharedSpaceName: defines the name of the shared space used to import the apps into prior to publishing. If the space doesn't exist, it'll be created. If the space exists, the user will be added to it with the required permissions (default: Monitoring - staging).
6. managedSpaceName: defines the name of the managed space the apps are published into for consumption/ alerts/ subscription use.If the space doesn't exist, it'll be created. If the space exists, the user will be added to it with the required permissions (default: Monitoring).
7. versionsToKeep: determines how many versions of each staged app is kept in the shared space. If set to 0, apps are deleted after publishing. If a positive integer value other than 0, that many apps will be kept for each monitoring app deployed (default: 0).

App management:

If the monitoring applications have been installed manually (i.e., not through this automation), then they will not be detected as existing. The automation will install new copies side-by-side. Any subsequent executions of the automation will detect the newly installed monitoring applications and check their versions, etc. This is due to the fact that the applications are tagged with "QCMA - {appName}" and "QCMA - {version}" during the installation process through the automation. Manually installed applications will not have these tags and therefore will not be detected.

FAQ

Q: Can I re-run the installer to check if any of the monitoring applications are able to be upgraded to a later version?

A: Yes. The automation will update any managed apps that don't match the repository's manifest version.

Q: What if multiple people install monitoring applications in different spaces?

A: The template scopes the application's installation process to a managed space. It will scope the API key name to `QCMA – {spaceId}` of that managed space. This allows the template to install/update the monitoring applications across spaces and across users. If one user installs an application to “Space A” and then another user installs a different monitoring application to “Space A”, the template will see that a data connection and associated API key (in this case from another user) exists for that space already. It will install the application leveraging those pre-existing assets.

Q: What if a new monitoring application is released? Will the template provide the ability to install that application as well?

A: Yes, but an update of the template from the template picker will be required, since the applications are hard coded into the template. The automation will begin to fail with a notification an update is needed once a new version is available.

Q:I have updated my application, but I noticed that it did not preserve the history. Why is that?

A: Each upgrade may generate a new set of QVDs if the data models for the applications have changed due to bug fixes, updates, new features, etc. The history is preserved in the prior versions of the application’s QVDs, so the data is never deleted and can be loaded into the older version. 

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.

How to purchase

You can purchase Qlik Replicate, Qlik Compose, and Qlik Enterprise Manager by contacting a local sales office.

How to obtain the license

Once you have completed the order and a deal has been signed, a license is delivered by email. You will receive a license.txt file. This file contains details such as the product expiration date (if any).

This usually happens within a day of Qlik receiving the order.

Where do I find my license?

If you lose access to the email holding the license, you can instead log on to the Qlik Support Portal an access the original case which includes your license details.

You can also find your license directly in the product after you have licensed it.

What does my license include?

Your license will allow you to:

• Run tasks using the endpoints specified. Example, if you have purchased an Oracle endpoint, you will be able to run tasks using an Oracle endpoint. 
• Grant you general access (not able to use the tool for QEM nor Compose)

To get a better understanding of what your individual license allows, review your license.txt file.

Qlik Replicate: 

license_type= (evaluation or permanent)
licensed_to= (your company name)
licensed_by= (the Qlik region responsible for providing the license)
serial_no= (serial internal reference)
expiration_date= (date of expiration)
hosts= (host names in which Replicate will run. If blank, means that any host can run)
source_types= (the source endpoints purchased by customer)
target_types= (the target endpoints purchased by customer)
features= (additional features)
version= (version of Replicate)
issue_date= (issue date)
checksum= (check sum so the engine can check validity)

Qlik Compose

Will in addition include: 

host_role: (DEV, TEST, PROD or “*” for all)
source_db_types: (applicable for Compose for Data Warehouses only)
dwh_type: (Databases that’ll be used as DWH)
dl_type: (Databases that’ll be used as DL)
number_of_dms: (total number of Data Marts)
number_of_developers: (available if host_role is DEV)
managed_dwh_size: (size of the DWH)

Qlik Enterprise Manager

Similar to Qlik Replicate.

There is one license for Qlik Enterprise Manager Monitoring and another license for Qlik Enterprise Analytics. 

Please note that in order to have Qlik Replicate servers added to your Qlik Enterprise Manager monitoring, they need also to have a valid license, otherwise you will get an “Unauthorized” error when adding a Qlik Replicate server.

How to I extend or modify my license?

Qlik Replicate allows you to modify your license directly through the Qlik Replicate UI. See Requesting a license.

How do I apply the Qlik Replicate, Qlik Compose, or Enterprise Manager license?

• Qlik Replicate: Registering a license 
• Qlik Enterprise Manager: Replication Management license 
• Qlik Compose: License settings 

You can also apply licenses to Qlik Replicate servers programmatically by using the QEM API REST calls as seen in PutServerLicense 

Can I apply the same Qlik Replicate license on DEV, QA, and Production?

Yes, you can apply the same license on all three environments. 

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