You can select a sheet to the landing page of the app by setting a default bookmark.

When you open the app, the expected landing page may not be displayed.

As well, when you open a sheet with a sheet action, the action might not get triggered.

Environment

• Qlik Sense Enterprise SaaS
• Qlik Sense Business

Resolution

The session needs to be terminated.

1. Close the browser or all opened tabs.
2. Wait for 30 minutes.
3. Log in to the tenant and open the app.

Cause 

The default bookmark with selection and landing sheet as well as sheet actions are applied once per session.

Qlik Sense SaaS keeps the session up to 30 minutes after closing the tab or tabs.

Related Content 

Setting a default bookmark to create an app landing page

NPrinting Initial Installation Fails with Error 0x080070643 (or similar)

Environment

• Qlik NPrinting all supported versions

Resolution

1. Ensure you have carefully reviewed and met the installation requirements. See Planning your deployment.
2. Ensure you have also carefully reviewed the companion NPrinting Product Release Notes (Release Notes) before installing.
3. The downloaded NPrinting install files must be in an 'unblocked' state
   
   
   
   
4. Ensure you have sufficient c:\drive space (NPrinting can only be installed on the c:\drive)
5. Antivirus software should be disabled 
6. The Windows Server hosting NP server is online to the internet (if offline, ensure all windows updates are performed 'before' attempting to install NPrinting server software)
7. The Windows Server hosting NPrinting has had all windows updates applied
8. The NP server computer is installed exclusively (no other Qlik Products or earlier versions of NPrinting (ie: NP 16) are installed or have been previously installed)
9. The Windows Server computer is a member of the same domain as the NPrinting Server service account
10. The intended NPrinting domain service user account used to install the NPrinting Server software 
    • is a member of the local administrators group Windows Qlik NPrinting Engine service administrator
    • has log on as a service > user rights assignment Windows Qlik NPrinting Server services administrator
    • is NOT restricted in any way by Active Directory group policy
    • is a member of the same domain as the NPrinting server computer

If any other version of NPrinting (ie NP 16 and earlier client server track) has been installed here previously or other unrelated software is installed, it would be recommended to reinstall Windows Server OS to ensure a clean start before installing NPrinting Server. (...or if this target Windows Server has been repurposed for use with NPrinting from some other function. It could already be damaged ie: damaged registry files).

*It is best to have a clean slate when installing Qlik NPrinting Server for the first time or if you suspect that the underlying Windows Server has become corrupted or damaged, or even when upgrading and Error 0x080070643 appears *

Related Information

• How to BackUp and Restore Qlik NPrinting Repositor... - Qlik Community - 1715863
• Qlik NPrinting Upgrade Steps and Best Practices
• Planning and Deploying NPrinting

パートナー様経由でのサポートケース対応について、以下の通り変更いたしました。

■背景
サポート対応をより円滑かつ迅速に進めるため、
パートナー様からご連絡いただく際の情報提供方法を見直しました。

■変更内容
2026年3月12日より、
サポートケースをご登録いただく際には、所定のテンプレートに沿った情報提供が必要となります。 

■目的
本テンプレートをご利用いただくことで、
調査を迅速に開始することが可能となり、対応時間の短縮につながります。

■サポートケース提出テンプレート 

[顧客名]
￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣
（顧客名）
 
[問合せ緊急度（理由）]
￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣
（Severityとその理由）

Severityの定義については以下をご確認ください。
https://assets.qlik.com/image/upload/v1712597297/qlik/docs/Legal/Policies/oem-msp-support-policy_xauitc.pdf
⇒1. Definitions

[環境情報 / 製品情報]
￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣
（製品名、バージョン情報も含む）

[お問い合わせ内容]
￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣

[添付ファイルの情報]
￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣

[Partner側で実施した調査内容]
￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣
 
[再現手順]
￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣

[再現ができない場合]
￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣
再現ができない場合は、その理由をご記載ください。

￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣

■テンプレートの各項目の詳細については以下をご参照ください。

・Qlik製品
https://community.qlik.com/t5/Official-Support-Articles/Partner-Guide-How-to-Prepare-and-Collaborate-with-Qlik-Data/ta-p/2524105

・QDI製品
https://community.qlik.com/t5/Official-Support-Articles/Partner-Guide-How-to-Prepare-and-Collaborate-with-Qlik-Data/ta-p/2534826

・Talend製品
https://community.qlik.com/t5/Official-Support-Articles/Partner-Guide-How-to-Prepare-and-Collaborate-with-Qlik-Talend/ta-p/2522146

Qlik Sense uses HTTP,  HTTPS, and WebSockets to transfer information to and from Qlik Sense.

The attached Webscoket Connectivity tester can be used to verify protocol compliance, indicating if a network policy, firewall, or other perimeter device is blocking any of the required connections.

If the tests return as unsuccessful, please engage your network team. 

The QlikSenseWEbsocketConnectivtyTester is not an officially supported application and is provided as is. It is intended to assist in troubleshooting, but further investigation of an unsuccessful test will require your network team's involvement. To run this tool, the Qlik Sense server must have a working internet connection.

Environment:

Qlik Sense Enterprise on Windows 

For Qlik Sense Enterprise on Windows November 2024 and later:

Since the introduction of extended WebSocket CSRF protection, using the WebSocket Connectivity tester on any version later than November 2024 requires a temporary configuration change.

1. Open the Proxy.exe.config stored in C:\Program Files\Qlik\Sense\Proxy\
2. Locate

   <add key="WebSocketCSWSHCheckEnabled" value="true"/> 

3. Change it to

   <add key="WebSocketCSWSHCheckEnabled" value="false"/> 

4. Restart the proxy
5. Run the WebSocket Connectivity tester
6. Revert the change

How to use the Websocket Connectivity Tester

1. Download the attached package or download the package from GitHub: https://github.com/flautrup/QlikSenseWebsocketConnectivityTester
2. Unzip the file
3. Login to the Qlik Sense Management Console
4. Create a Content Library
   
   
   1. Go to Content libraries 
   2. Click and Create New
   3. Name the Content Library: WebSocketTester
   4. Verify and modify the Security Rule
      
      Note that in our example, any user is allowed to access this WebSocketTester.
      
      
      
      
   5. Click Apply
      
      
5. Click Contents in the Associated items menu
6. Click Upload
7. Upload the QlikSenseWebsocketTest.html file.
8. Copy the correct URL from the URL path
   
   
   
   
9. Open a web browser (from any machine from which you wish to test the WebSocket connection).
10. Paste the URL path and prefix the fully qualified domain name and https. 
    
    Example: https://qlikserver3.domain.local/content/WebSocketTester/QlikSenseWebsocketTest.html
    
    

What to do if any of them fail?

Verify that WebSocket is enabled in the network infrastructure, such as firewalls, browsers, reverse proxies, etc.

See the article below under Related Content for additional steps.

Related Content

• Hub access times out with: Error Connection lost. Make sure that Qlik Sense is running properly 

After upgrading from Talend 7.3 to Talend 8 (R2025-10), it includes the Camel 4 update, and a change in the cSetHeader component. In previous Talend 7.x, JSONPath evaluation generated a correctly formatted JSON header, however, in Talend 8, the same configuration produces a non-JSON representation where double quotes are stripped from the resulting object.

For example

Source Input

{ "META": {"Correlation_ID": "B","BGM_ACTION_CODE": “A”},
 "STATUS": {"ADD_R_UPDATE_SUCCEEDED": “Y”},
 "ERR": [ {"field": "ADD","keyword": "custOrgMustHaveAdd", "entity": “ORGANI” }]
}
 

cSetHeader Component Setting

Output in  Talend 7 (Correct)

[{"field":"ADD","keyword":"custOrgMustHaveAdd","entity":"ORGANI"}]

cSetHeaderOutputTalend7

Output in Talend 8 (Invalid JSON format with out Double Quotes)

[{field=ADD, keyword=custOrgMustHaveAdd, entity=ORGANI}]

cSetHeaderOutputTalend8

Resolution

Install the latest R2025-11 (or newer) update for both Talend Studio and Talend Runtime, where the corrected behavior has been implemented.

Cause

This behavior stems from changes in the underlying JSON processor, specifically, the shift from json-smart to JacksonJsonProvider, which modifies how JSONPath results are serialized.

The issue aligns with the upstream Camel defect jira issue reported here:
CAMEL-16389 | issues.apache.org 

Environment

Talend ESB 

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

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

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

Content

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

General Expectations Before Submitting a Case

Isolate What Is Affected

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

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

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

Provide Product and Version Information

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

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

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

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

Reproduce the Issue in Your Environment

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

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

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

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

See the Release Note for the resolved issues.

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

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

Always Provide Complete (Not Partial) Logs

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

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

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

Additionally:

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

Describe What You Have Already Investigated

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

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

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

Sharing this thought process:

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

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

Submit All Related Files You Investigated Or Used For Replication

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

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

This includes (but is not limited to):

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

Submit the Case Using Your Partner Account

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

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

Partner Case Submission

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

Partner Case Submission Template

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

Summary of the Problem

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

Clearly describe the issue, including:

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

Specify if applicable:

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

Find your Qlik Cloud Subscription ID and Tenant Hostname and ID

Customer Information

Only include what is needed based on the case type.

Files Attached

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

Summary of your Investigation

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

Examples:

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

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

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

Environment

• Qlik Data Integration Products

In an effort to further clarify the differences between the Qlik Sense editions available and how Multi-Cloud ties in with those, see Qlik Sense at a glance.

A brief summary is provided in this article.

Qlik Sense is available on SaaS (Qlik Cloud) and Windows. 

Qlik Cloud allows for two different subscription types: Enterprise and Business. Qlik Sense Enterprise is the full version of Qlik Sense, supporting a full spectrum of analytics use cases on a multi-cloud platform. Qlik Sense Business is a SaaS solution that brings the power of Qlik’s third-generation analytics platform to groups, teams, and businesses that want to quickly operationalize analytics and make data-driven decisions.

Qlik Sense Enterprise on Windows is deployed on-premise and client managed. You can distribute Qlik Sense apps to cloud environments, using Qlik Sense Enterprise multi-cloud capabilities and share user management between a Qlik Cloud instance and a client-managed instance. This is only possible with a Qlik Sense Enterprise subscription.

Related Content:

Get started with Qlik Sense Enterprise SaaS 
Introducing Qlik Sense Enterprise on Windows 
Introducing Qlik Sense Business 

When using an Amazon S3 as a target in a Qlik Replicate task, the Full Load data are written to CSV, TEXT, or JSON files (depending on the endpoint settings). The Full Load Files are named using incremental counters e.g. LOAD00000001.csv, LOAD00000002.csv. This is the default behavior. 

In some scenarios, you may want to use the table name as the file name rather than LOAD########.

This article describes how to rename the output files from LOAD######## to <schemaName>_<tableName>__######## format while Qlik Replicate running on a Windows platform.

In this article, we will focus on cloud types of target endpoint (ADLS, S3, etc...) The example uses Amazon S3 which locates remote cloud storage.

This customization is provided as is. Qlik Support cannot provide continued support for the solution. For assistance, reach out to Professional Services.

Resolution

1. Open and modify repctl.cfg 
   
   Default file location: C:\Program Files\Attunity\Replicate\bin
   
   Set enable_execute_user_defined_commands from false to true 
   
   Example: "enable_execute_user_defined_commands": true,
   
   
2. Download and run the AWS CLI MSI installer for Windows (64-bit) (aws-cli/2.13.9  is used in this sample)
3. Set up the AWS CLI, and Configuring using AWS CLI commands. Sample steps of short-term credentials: 
   C:\Users\demo>aws configure
   AWS Access Key ID [None]     : DEMO~~~~~~~~~~~~UXEM
   AWS Secret Access Key [None] : demo~~~~~~~~~~~~ciYW7pugMTv/0DemoSQtfw1m
   Default region name [None]   : us-east-1
   Default output format [None] : json
4. Restart the Qlik Replicate Server service. 
   
   
5. Create a text/batch file named myrename_S3.bat and save it in the Qlik Replicate Server folder: C:\Program Files\Attunity\Replicate\bin
   
   Content of the file:
   

   @Echo on
   setx AWS_SHARED_CREDENTIALS_FILE C:\Users\demo\.aws\credentials
   for  %%a in (%1) do set "fn=%%~na"
   echo %fn%
   set  sn=%fn:~4,8%
   echo %sn%
   aws s3 mv s3://%1 s3://qmi-bucket-1234567868c4deded132f4ca/APAC_Test/%2.%3/%2_%3__%sn%.csv

   where  C:\Users\demo\.aws\credentials is generated in above step 3. The values are obfuscated in the above sample.

6. Set the Amazon S3 Target endpoint and configure it with the following settings: 
   
   

   General
       Bucket name       : qmi-bucket-1234567868c4deded132f4ca
       Bucket region     :  US East (N. Virginia)

       Access options   : Key pair
       Access key            :  DEMO~~~~~~~~~~~~UXEM
       Secret key             :  demo~~~~~~~~~~~~ciYW7pugMTv/0DemoSQtfw1m

                Target folder        : /APAC_Test

1. 
   

   
   Advanced
       Post Upload Processing, choose "Run command after upload"
       Command name  : myrename_S3.bat
       Working directory: leave blank
       Parameters             : ${FILENAME} ${TABLE_OWNER} ${TABLE_NAME}
   

   

    

   7. Startup or Reload the Full Load ONLY task and verify the file output.
   
   By using command "aws s3 ls", it will typically looks like:
   

   C:\Users\demo>>aws s3 ls s3://qmi-bucket-1234567868c4deded132f4ca/APAC_Test --recursive --human-readable --summarize
   2023-08-14 11:20:36 0 Bytes APAC_Test/
   2023-08-15 08:10:24 0 Bytes APAC_Test/SCOTT.KIT/
   2023-08-15 08:10:28 9 Bytes APAC_Test/SCOTT.KIT/SCOTT_KIT__00000001.csv
   2023-08-15 08:10:24 0 Bytes APAC_Test/SCOTT.KIT500K/
   2023-08-15 08:10:34 4.0 MiB APAC_Test/SCOTT.KIT500K/SCOTT_KIT500K__00000001.csv
   2023-08-15 08:10:44 4.0 MiB APAC_Test/SCOTT.KIT500K/SCOTT_KIT500K__00000002.csv
   2023-08-15 08:10:54 4.0 MiB APAC_Test/SCOTT.KIT500K/SCOTT_KIT500K__00000003.csv
   2023-08-15 08:11:05 4.0 MiB APAC_Test/SCOTT.KIT500K/SCOTT_KIT500K__00000004.csv
   2023-08-15 08:11:15 4.0 MiB APAC_Test/SCOTT.KIT500K/SCOTT_KIT500K__00000005.csv
   2023-08-15 08:11:24 2.7 MiB APAC_Test/SCOTT.KIT500K/SCOTT_KIT500K__00000006.csv

   Total Objects: 10
   Total Size: 22.7 MiB

   
   Where SCOTT is the source table schema name, KIT/KIT500K are source table name, 0000000<n> is the unique incremental number.
   
   You can tailor the myrename_S3.bat file for any particular needs.

Environment

Qlik Replicate  
Amazon S3 target

Related Content:

Qlik Replicate and File target: How to rename output files LOAD######## to table name format on Wind...
Qlik Replicate and File target: How to rename output files LOAD######## to table name format on Linu...

Qlik Replicate and ADSL target: How to rename output files LOAD######## to table name format (Replicate runs on Windows)

Description

• Error "Object reference not set to an instance of an object" when previewing NPrinting Designer Excel Template Editor reports that contain merged cells

Diagnosis:

• After upgrade, open an NPrinting Report in the NP designer and preview a report that his known to contain merged cells
• Preview the Report
• Error encountered "The preview request failed with message: Object reference not set to an instance of an object"

Environment

• Discovered following an upgrade from older unsupported NP versions (NP November 2019) to Current Supported NP versions

Resolution

• Please note that this issue has been resolved and will be available in NPrinting May 2022 SR 4.
• Keep an eye on the Qlik Community Downloads site and Product release notes for new product and service releases.

Workaround:

• None at this time

Cause

• Product Defect ID: OP-95768

Related Content

• Release Notes | Qlik Community
• Downloads | Qlik Community

For Qlik Talend On-premises Solution, when using global context values in all jobs, If you want to change the file path values to replace d:/ with t:/, you can propagate the change to all jobs in the Studio.

 
How about Qlik Talend Cloud and Hybrid Solutions? This article provides a brief introduction to changing the value of context parameters and propagating the change to all Tasks in Talend Cloud.

How To

You can use this API to update artifact parameters

Put https://api.eu.cloud.talend.com/orchestration/executables/tasks/{taskid}

In the body, set the paramters you want to update:

Example: change the ContextFilePath": from "C:/Franking/in.csv" to  "h:/Franking/in.csv")

{
 "name": "contextpath",
 "description": "CC",
 "workspaceId": "61167bef18d7d656bfae071d",
"artifact": {
   "id": "689b5d04febbe74489779c31",    
   "version": "0.1.0.20251208032554"
 },
 "parameters":{
"ContextFilePath": "h:/Franking/in.csv"
}
}

To maintain context values better in the long run for multiple jobs, create a Connection in Talend Cloud. This way, all context in the job can be updated by updating the file name in the Qlik Talend Management Console Connection as opposed to running the API multiple times. For information on how to set up a connection, see Managing connections.

Environment

• Talend Cloud 
• Talend Studio 

Microsoft will deprecate Change Data Capture (CDC) components by Attunity. See SQL Server Integration Services (SSIS) Change Data Capture Attunity feature deprecations | microsoft.com for details.

Will this affect Qlik Replicate? 

Resolution

This announcement does not affect Qlik Replicate. It is only relevant to the product "Change Data Capture (CDC) components by Attunity".

Microsoft distributes and provides primary support for this product. Qlik Replicate's functionality will remain the same.

Environment

• Qlik Replicate

If using the tap-shopify connector in Stitch for the orders stream, you may encounter the following error:

"An error occurred with the GraphQL API"

Resolution

To resolve the error:

• Adjust Anchor/Extraction Time
  Change the extraction time to avoid overlap with any existing bulk operation.
• Use a Single Stitch Connection per Shopify Store
  This minimizes the chance of simultaneous extractions that can trigger the error.
• Check for Other Tools Using Shopify Bulk API
  If other platforms or integrations are pulling data from Shopify, co-ordinate schedules to prevent conflicts.
  
  

Cause

Why This Happens

This is a Shopify platform constraint, not a Stitch limitation.

The Shopify Bulk API has an important restriction that only one bulk operation per type (e.g., orders) can run at a time per shop.

This means: If a bulk job is already running, any new request of the same type will fail. Overlapping jobs from multiple Stitch connections or other platforms can trigger this error.

When You Might See This Error

You may encounter this message if:

• A previous bulk operation hasn’t completed.
• Multiple Stitch connections are extracting from the same Shopify shop.
• Another platform or integration is using Shopify’s Bulk API at the same time.

Related Content 

Shopify Bulk API Documentations:
https://shopify.dev/docs/api/usage/bulk-operations/queries#limitations
Bulk operations with the GraphQL Admin API 

Environment

Stitch 

When installed in Linux deployment server, those two folders are allocating a lot of space in - /opt partition.
- /opt/TalendRemoteEngine
- /opt/TalendRuntime-8.0.1-R2025-02-RT

How to purge and keep under control the space allocated in - /opt partition?

How To

Cleaning Talend Remote Engine (RE) Cache and Logs

1. Stop the Remote Engine.
2. Delete the following contents:
   1. Temporary files:
      <TalendRemoteEngine>/data/tmp
   2. Cache files:
      <TalendRemoteEngine>/data/cache
   3. Log files (delete based on your retention policy):
      <TalendRemoteEngine>/data/log
3. Restart the Remote Engine.

Cleaning Up KAR Files from Talend Runtime Server
Please follow the steps in this article to remove or clean up KAR files:
How to Remove / Clean Up KAR Files from Talend Runtime Server

Related Content 

For automated clean-up, refer to the following documentation: Understanding the Talend Remote Engine Clean-up Cycle

Environment

• Talend Cloud 
• Talend ESB 

After activating Stitch with SSO login using Azure, current users can log in without issue. However, new users added to the Azure AD cannot see Stitch.

Resolution

A new user must log in through the My Apps Portal:

1. Go to: https://myapps.microsoft.com
2. Sign in using the correct work account
3. Locate and click on the Stitch tile
4. The new user is now authenticated using Azure SSO

Trigger provisioning in Stitch and automatically create the user in Stitch (if configured correctly).

Other Identity Providers (Idps) function similarly. These are their respective URLs:

• Google Workspace
   https://accounts.google.com, then click the Google Apps menu
• Okta
  https://<your-company>.okta.com/app/UserHome 
• Onelogin
  https://<your-company>.onelogin.com/portal 
• PingFederate
  https://apps.pingone.com

Cause

Stitch uses Just-in-Time provisioning. 

This means that: A user is not created in Stitch automatically when added to Azure AD. Instead, a user is only provisioned in Stitch when they log in for the first time via SSO.

Environment

Stitch 

In Talend Studio 8.0 (version R2025‑05), tDataQualityRules component fails to refresh data quality rules defined in Talend Cloud Data Stewardship. When attempting to refresh, the UI remains unresponsive and does not load updated rules.

The Studio logs record an Unhandled event loop exception and a 400 Bad Request HTTP error when retrieving a rule artifact artifact .jar file from the rule repository.

 
Caused by: org.springframework.web.client.HttpClientErrorException$BadRequest: 400 Bad Request
<Resource>/eu-central-1-minio-production/repositories/<UUID>/rules/1753780XXXXX/rules-1753780XXXXX.jar</Resource>
<Code>InvalidRequest</Code>

Resolution

Please update rule to the latest version in all sub-jobs and use  TDC to download jar files.

In the URL field of tDataQualityRules component basic setting, updating it to https://tdc.eu.cloud.talend.com

Cause 

The error is caused by a malformed or stale artifact path to repository where Talend Studio is attempting to fetch a rule artifact .jar file from.

It is a known issue that cannot connect to TDS Gateway https://tds.us.cloud.talend.com/ to download jars

Related Content 

troubleshooting-tdataqualityrules-with-tds

Environment

• Talend Data Stewardship 

To resolve login issues with your Qlik Stitch account:

• Verify you are using the correct login details
• Clear your browser's cache and cookies and try accessing your account using incognito mode to rule out browser cache issues
• Disable ad-blocking plugins temporarily

Should this not resolve the issue, please do not hesitate to contact our Support team.

To prevent account lockout, refrain from submitting multiple password reset requests within a single day.

Environment

• Stitch 

Sometimes, for the database integration, like PostgreSQL, MongoDB, etc., you may encounter the following error.

2021-03-03 15:55:20,221Z   main - INFO Exit status is: Discovery succeeded. Tap failed with code -9. Target succeeded.

Resolution

To help with the above scenario, we have two non-customer-facing settings we can help to set. Those are the Incremental limit and the Itersize values.

Incremental Limit – Chunks full table and incremental queries into multiple explicit queries by adding a LIMIT X clause to each. This would reduce the load on the DB to prepare result sets if that’s an issue. As mentioned above, by default, our full table and incremental queries do not issue a limit. By adding an incremental limit, we are now forcing the integration to request "batches" of x number of data. This is in hopes that it can alleviate the burden on the source and allow for the query to complete.

Itersize – This adjusts the number of rows fetched per round trip of a streaming result set for the queries themselves (defaults to 20k rows at a time). It controls the maximum rows fetched in a batch.

If you face this issue, please reach out to us, and we can set up alleviation for you.
How-to-contact-Qlik-Support

Cause

Generally, these -9 errors indicate that the tap is running out of memory when trying to perform an extraction. By default, our full table and incremental queries do not issue a limit. As a result, we wait for the query to complete on your server and in some instances, if the resulting data is quite large, it can terminate, resulting in a connection close error or something similar, like a memory error.

Environment

Stitch