Question

How can we retrieve artifact information from Talend update website? For instance, for artifact "accessors-smart-2.4.11.jar", we can use the following URL to query its information: https://search.maven.org/solrsearch/select?q=a:accessors-smart+AND+v:2.4.11&rows=1&wt=json

Does Talend also offer a similar feature for its artifacts?

Answer

Talend update website is built on Nexus and utilizes the Lucene search API, as demonstrated in the following example:

https://talend-update.talend.com/nexus/service/local/lucene/search?a=accessors-smart&v=2.4.11

For further details on the Lucene search API, please refer to: Nexus Indexer Lucene Plugin REST API | repository.sonatype.org

Environment

• Talend Data Integration 

After upgrading to Qlik Talend Cloud Enterprise Edition R2025-08, some users reported that the tClaudeAIClient component was missing from the Talend Studio Palette.
Despite attempts to search for the component in the Palette or import it manually, they were unsuccessful.

Resolution

To restore the tClaudeAIClient component in Talend Studio, follow the steps below:

1. Open Talend Studio.
2. Navigate to Feature Manager by selecting "Help" > "Install Additional Packages" from the top menu or by using the shortcut icon for the Feature Manager on the Studio toolbar.
3. In the Feature Manager window, go to Components.
4. Locate EmbeddingAI under the available component families.
5. Select EmbeddingAI, then click Download or Install.
6. Once installation completes, restart Talend Studio.

After restarting, verify that the tClaudeAIClient component is available in the Palette under the AI family.

Cause 

The tClaudeAIClient component is a member of the AI family, which is offered through the EmbeddingAI optional feature. However, this feature may not be automatically installed or enabled by default, as it depends on the user's Studio configuration and feature synchronization settings.

Additional Notes

The EmbeddingAI package includes additional AI-related components beyond tClaudeAIClient.
If the component still does not appear after installation, ensure your Studio is synchronized with your Qlik Talend Cloud license and feature repositories.
For enterprise environments with restricted update policies, check with your Talend administrator to confirm access to optional feature downloads.

Environment

• Qlik Talend Cloud Enterprise Edition R2025-08 and later

• Talend Studio (Cloud or Local Installation)

To troubleshoot an issue, it may be necessary to enable ODBC trace logging for Linux Servers.

To enable tracing:

1. Locate the odbcinst.ini file
   The file is typically located at /etc/odbcinst.ini
2. Edit the file by opening it in a text editor
3. Find the [ODBC] section.
4. Add or modify the following lines:
   
   Below the [ODBC] section:
   
   Trace=Yes
   TraceFile=/path/to/your/trace.log
   
   Replace with the desired path and filename for your log.
   
   
5. Save the file
6. Restart the Qlik Replicate service
7. Give 777 permissions to the directory where TraceFile is located so that Qlik Replicate can create the log file
8. Reproduce the issue. Run your application to generate the trace log.

To disable tracing:    

Once you are finished, repeat the steps and set Trace=Yes to Trace=No in the odbcinst.ini file.

odbcinst.ini example:

[ODBC Driver 18 for SQL Server]
Description=Microsoft ODBC Driver 18 for SQL Server
Driver=/opt/microsoft/msodbcsql18/lib64/libmsodbcsql-18.1.so.2.1
UsageCount=1
[ODBC]
Trace=Yes
TraceFile=/odbctrace/odbctrace.log
TraceOptions=3    

Environment

• Qlik Replicate

The Service Authentication method is chosen during the initial QlikView installation procedure.

Two options are available:

• QlikView Administrators Group (default)
• Digital certificates 

See Installing QlikView Server for more information.

To verify the currently in use Service Authentication method:

1. Open the QlikView Management Console (QMC)
2. Go to System 
3. Go to About
4. Locate Service authentication 
   
   If set to AD, the QlikView Administrators Group is in use. 
   
   

Related Content

Change QlikView Services communication from Certificate Trust to Windows Group Authentication (UseWinAuthentication) 

Environment

• QlikView

While working in an app, users may be unable to access the Expression editor. Clicking the fX (expression) button results in nothing happening. 

Both the right-side property pane and the variable editor are affected.

Resolution

The app might contain bookmarks that, for some reason, lack titles. Without titles, these bookmarks can cause unexpected behavior. If the bookmarks are private, only the owner of the bookmarks will be affected. 

Workaround:

1. Open the app's Bookmarks section (A) and identify bookmarks without titles (B)
   
   
   
   
2. Access the bookmark's Details 
   
   
   
   
3. Select Edit Details 
   
   
   
   
4. Add a Title to the bookmark
   
   
   
   
5. Click Done

Environment

• Qlik Cloud Analytics

A Professional or Full entitlement was removed without any action from the tenant administrators.

Going to the Administration activity center and reviewing Events by filtering for the Event Type "com.qlik.license.assignment.deleted" or "com.qlik.license.assignment.updated" shows no activity.

Resolution

Always align entitlements between your environments.

Cause

If the same Signed License Key is also used by another tenant or on a version of Qlik Sense Enterprise for Windows, any change from those other environments will be synchronized to your tenant.

Because the action was not performed on the tenant itself, the tenant's Events section (or the Audit APIs) won't show them.

Environment

• Qlik Cloud Analytics

With a Unified license (formerly called Dual Use License) the legacy QlikView license is complemented with a Qlik Sense license that can be applied to the QlikView server as it includes QlikView entitlement license attributes. Such license needs to be activated with the Signed License Key (SLK). When a customer enters an Analytics Modernization Program (AMP, formerly known as Dual Use program), QlikView CALs (e.g. Named User CALs, Document CALS, Session CALs and Usage CALs) are converted into Professional User, Analyzer User,  and Analyzer Capacity User allocations based on the Analytics Modernization Program conversion ratios.

Here are two scenarios:

I. If a customer transitions to AMP with on-premise (client-managed) Qlik software (e.g. converts to the perpetual estate or convert to subscription Qlik Sense Enterprise on Windows), a Unified License containing the converted quantity of Professional Users, Analyzer Users and Analyzer Capacity would be delivered. This license contains a customized Qlik Sense Enterprise Signed License Key (SLK) which can also be deployed on QlikView Server and/or QlikView Publisher. If a user is assigned a Professional or Analyzer user license, this assignment information is synchronized to all Qlik Sense and QlikView deployments activated using this Unified License key. As such one user just needs one license to access the entire Qlik software platform (regardless if it is Qlik Sense or QlikView).

In this scenario, as long as the QlikView Server and Qlik Sense edition use the same Identity Provider (IdP) the user can access apps on both environments consuming only one user license allocation.

If the user license is reallocated in any of the systems to a different user, the same will occur across both QlikView and Qlik Sense environments.

II. If a customer transitions to AMP with Qlik Sense Enterprise SaaS add-on, a Qlik Sense Enterprise SaaS tenant may use a Unified License  for the on-premise deployment. The customer is able to upload QlikView document prepared by the on-premise QlikView software directly into Qlik Sense Enterprise SaaS for distribution.

A QlikView Server or a Qlik Publisher software can be activated in two ways:

1) Using a legacy method with 16-digit QlikView license key and the corresponding control number

2) Using a modern Unified License with Signed License Key containing needed QlikView Server and Publisher Service attribute(s). In this latter scenario, user license assignment (Professional/Analyzer) and analyzer capacity would be synchronized with other deployments using the same Signed License Key as it is done in the Unified License model

If the customer opts to remain in Perpetual licensing, the existing QlikView license model can be retained. Otherwise, if the customer opts for conversion into Subscription licensing model, a set of QlikView subscription license attributes mirroring the existing QlikView perpetual license key setup would be delivered such that the customer switch to the subscription QlikView keys without the need for an immediate migration project towards using Unified licensing.

Note: Please note that Qlik is no longer starting clients on the Perpetual license model. See End of Perpetual License Sales 

Environment:

• QlikView 
• Qlik Cloud 
• Qlik Sense Enterprise on Windows 
   

Related Content:

• How to Apply an unified Signed License Key for QlikView and Qlik Sense
• Qlik Multi-Cloud Frequently Asked Questions (FAQ)

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

The Qlik Sense System_Repository log file will read:

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

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

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

Resolution

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

Take a backup of your environment before proceeding.

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

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

Related Content

Show base memory size of apps in QMC

Internal Investigation:

QB-22795
QB-24301

Environment

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

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

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

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

Content

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

General Expectations Before Submitting a Case

Isolate What Is Affected

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

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

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

Provide Product and Version Information

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

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

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

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

Reproduce the Issue in Your Environment

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

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

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

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

See the Release Note for the resolved issues.

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

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

Always Provide Complete (Not Partial) Logs

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

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

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

Additionally:

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

Describe What You Have Already Investigated

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

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

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

Sharing this thought process:

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

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

Submit All Related Files You Investigated Or Used For Replication

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

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

This includes (but is not limited to):

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

Submit the Case Using Your Partner Account

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

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

Partner Case Submission

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

Partner Case Submission Template

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

Summary of the Problem

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

Clearly describe the issue, including:

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

Specify if applicable:

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

Find your Qlik Cloud Subscription ID and Tenant Hostname and ID

Customer Information

Only include what is needed based on the case type.

Files Attached

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

Summary of your Investigation

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

Examples:

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

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

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

Environment

• Qlik Data Integration Products

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

Content

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

What's New

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

2.1.0 September 2025 Release Notes

Known Limitations (2.1.0)

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

2.0.0 May 2025 Release Notes

Known Limitations (2.0.0)

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

1.4.0 December 2023 Release Notes

Known Limitations (1.4.0)

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

1.3.0 May 2023 Release Notes

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

When is a preloaded app unloaded? 

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

App cache time

To set or verify App cache time:

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

Time to live

To set or verify Time to live:

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

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

Environment

• Qlik Sense Enterprise on Windows

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

Default ruleset:

Resolution:

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

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

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

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

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

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

Resolution

There are three options to slove this issue

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

Disable SNI Host Check

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

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

jetty.ssl.sniRequired=false

and 

jetty.ssl.sniHostCheck=false

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

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

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

  

Resolve IP to Hostname

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

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

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

Try this API call at the command line:

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

or

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

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

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

Cause

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

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

Related Content 

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

Environment

Talend ESB 

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

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

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

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

Resolution

Run the following SQL command in Snowflake:

ALTER USER STITCH_USER SET DEFAULT_ROLE = STITCH_ROLE;

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

Cause

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

Environment

• Qlik Stitch

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

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

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

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

Full Automation

Variables used in the template:

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

Automation structure:

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

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

Related Content

Export Qlik Sense Apps to GitHub

Environment

Qlik Cloud 
Qlik Automate 

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

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

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

The lastGenerated.log will contain messages similar to:

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

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

Resolution

Change Build Type to Microservice.

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

Cause

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

Environment

• Qlik Talend Studio

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

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

Resolution

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

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

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

Cause

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

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

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

Environment

• Qlik Stitch

A NetSuite Suite Analytics integration encounters the following error: 

Failed to login using TBA

Resolution

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

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

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

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

Cause

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

Environment

• Qlik Stitch

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

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

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

What action do I need to take?

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

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

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

Environment

• Qlik Talend Cloud