Qlik Release Notes

May 7, 2026

New permission added for the engine assignment feature

The application engine assignment feature already allows permanent placement of applications on selected compute engine sizes. With this release, we're adding a new permission: Manage engine assignments for applications.

This permission lets you delegate engine assignment management to specific users without giving them full Tenant Admin or Analytics Admin rights. The permission is available only through custom roles and isn't included in the User Default permissions.

Assigning engines to improve application performance

Some functionality may be rolled out in phases and not immediately available in all regions.

May 7, 2026

Changes to Analyzer user access

To simplify the permission model and align with capacity-based subscriptions, the following Analyzer user capabilities have been updated:

• Analyzer users now have the same access as Professional users when they have the Can contribute role in managed spaces.
• Analyzer users with any Can edit role can now create private sheets in shared spaces.
• Analyzer users can no longer update application metadata in shared spaces.

Managed space permissions for users with Analyzer entitlement

Shared space permissions for users with Analyzer entitlement

Some functionality may be rolled out in phases and not immediately available in all regions.

May 7, 2026

Changes to scheduled automations

In support of scheduler improvements for Qlik Automate, changes are coming to scheduled automations. This begins with improvements to how the next scheduled run is shown in the Automation history view, and changing the minimum scheduling period to one minute, as announced in January 2026. Customers with schedules with second grain intervals will see these rounded to the nearest minute with this change.

For more information, see Qlik Automate: 30-second interval deprecation on Qlik Community.

Some functionality may be rolled out in phases and not immediately available in all regions.

May 5, 2026

Configurable maximum run time for automations

Qlik Automate now lets you configure the maximum run time for your automations, giving you more control over how long an automation is allowed to execute before it stops.

Previously, synchronous triggered automations had a fixed limit of 55 seconds, which could cause runs to fail when dependent services responded slowly.

You can now configure the limit for synchronous triggered automations from 55 seconds up to 5 minutes (default: 55 seconds). For all other automation types, you can set the limit up to 4 hours. Configure this in each automation’s settings.

Default values are unchanged: 55 seconds for synchronous triggered automations and 4 hours for all other automation types. Existing automations are not affected unless you update the setting.

For more information, see Navigating the user interface.

Some functionality may be rolled out in phases and not immediately available in all regions.

May 5, 2026

Select a branch for cross-project data sources

When consuming data from another project in a transform or data mart task, you can now select which branch of the referenced project to use as the source. The default branch is main. This lets you build stable prod-to-prod pipelines and isolated dev-to-dev pipelines across projects under version control.

Building cross-project pipelines

Some functionality may be rolled out in phases and not immediately available in all regions.

May 5, 2026

Bidirectional glossary term relationships

When you define a relationship between two glossary terms, the inverse relationship now automatically appears on the related term as well.

For example, if you relate Active Customer to Customer using the Is a relationship type, Customer will now display Has subtype: Active Customer — without any additional steps.

Relationship applied

Relationship displayed on related term

See also

See also

Synonym

Synonym

Replaced by

Replaces

Is a

Has subtype

Defined by

Defines

Previously, term relationships were only visible on the term where they were applied. With this update, stewards get a complete and consistent view of how terms relate to one another across the glossary, reducing the need to manually maintain relationships on both sides.

Creating terms and categories

Some functionality may be rolled out in phases and not immediately available in all regions.

April 29, 2026

Improved error messaging for time series experiments

When a time series experiment fails, customers now get specific, actionable error messages instead of generic failures. Errors identify exactly which groups, columns, or time periods caused the issue and explain how to fix it. This directly reduces support escalations and lets users resolve data problems on their own — no ticket required.

Working with multivariate time series forecasting

Not supported in Qlik Cloud Government.

Not supported in Qlik Cloud Government - DoD.

Some functionality may be rolled out in phases and not immediately available in all regions.

April 29, 2026

Qlik Talend Cloud - Data Integration improvements

Customers who are using Qlik Data Gateway - Data Movement need to upgrade to 2025.11.40 or later to benefit from these improvements. For upgrade instructions and a list of resolved issues, see Upgrading the Data Movement gateway installation.

Databricks driver rebranding

To align with Databricks, the driver for working with the Databricks connector has been rebranded.

To prevent tasks from failing, customers working with the Databricks connector must upgrade their driver. You can do this automatically using the driver setup utility (recommended) or manually. For instructions, see Driver setup. If you choose to install the driver manually, make sure to edit the odbcinst.ini file according to the instructions.

Support for new Snowflake and Google BigQuery driver versions

This version introduces support for the following driver versions:

• Snowflake: Snowflake ODBC driver 3.15.0 (64-bit)
• Google BigQuery: Simba ODBC driver version 3.1.6.1026

Support for the Databricks VARIANT data type

From this version, the following data types will be mapped to the Databricks native VARIANT data type:

• STRING
• WSTRING
• NCLOB
• CLOB

Requires Databricks Runtime 15.4 or later

Some functionality may be rolled out in phases and not immediately available in all regions.

April 28, 2026

Pivot table exploration

The much long awaited table exploration has arrived for the new Pivot table. Enjoy the ability to move dimensions and measures between rows and columns as a view user. Just as with the Straight table the developer can set up alternative dimensions and measures so that the end user can pick and choose to create his own custom report. The data section has the new look feel with single panel for both current and alternative items.

Creating pivot tables (Pivot)

Some functionality may be rolled out in phases and not immediately available in all regions.

April 28, 2026

Select by visible points in map charts

You can now configure your map charts to make selections in your application based on the visible points from a field. The new Spatial index operation in GeoOperations indexes your point data for use with your map chart. As you move focus in the map chart, selections are made from your selected point data field. Auto select visible makes it possible to display and interact with large map layers that would otherwise be too large to render.

Spatial index

Setting the zoom and selection behavior for maps

Some functionality may be rolled out in phases and not immediately available in all regions.

April 22, 2026

New Direct Access gateway version (1.7.13)

Direct Access gateway 1.7.13 introduces both new and enhanced features, and resolves several issues. For upgrade instructions and a list of resolved issues, see Upgrading the Direct Access gateway installation

This version introduces new and enhanced functionality as well as several bug fixes.

Extended authentication support

The following connectors now support Single Sign-On (Kerberos) authentication:

• Apache Hive
• Cloudera Impala
• Teradata
• Microsoft SQL Server

In addition, the Teradata connector now supports LDAP authentication.

Improved handling of File connector reloads

The Analytics engine would sometimes cache connections from earlier sessions and send a request to a pod that had been requested to shutdown. This would cause reloads to fail with the following error:

Connector error: data loading error (DirectAccess-4008)

From this version, reload requests to a pod that is no longer active will be rejected and routed to an available pod.

Improved reload measurement logging

Reload measurement logging has been improved. This will allow both customers and Qlik Support to gain further insights into reload performance.

As part of the improvements, the logging level will now be INFO and the log message has been adapted for use with the Direct Access gateway monitoring tool. Additionally, the following information will now be shown in the log:

• Percentage of the reload time spent on Web Socket transfer.
• A rough estimation of the throughput between the data source and Direct Access gateway.
• A rough estimation of the throughput between the Direct Access gateway and Qlik Cloud.

Ability to set how many rows to fetch per bulk when using the ODBC (via Direct Access gateway) connector

A new Number of rows to fetch per bulk option has been added to the ODBC (via Direct Access gateway) connector. While the default value is optimal for most scenarios, if you encounter significant performance issues, adjusting this value might help.

Row count validation during reloads

The row count from all non-File Direct Access gateway connectors (the number of rows it reads) will now be validated to ensure that it matches the number of rows sent to the engine.

If a mismatch is detected, the reload will fail with an appropriate error, thereby preventing inconsistent data loading.

Improved error handling of async commands

Identification and handling of response errors resulting from failed async commands has been improved. This enhancement will facilitate better troubleshooting of async command failure.

Some functionality may be rolled out in phases and not immediately available in all regions.

April 21, 2026

Configuring user session timeouts

Tenant administrators can now manage signed-in user sessions with two new settings:

• Session inactivity timeout – defines how long a user can be inactive before the session ends.
• Maximum session lifetime – sets the maximum duration of a user session, regardless of activity.

These options give you more control over security and user experience—so yes, you can now take that extra-long coffee break.

This enhancement is based on feedback from our users through this Qlik Ideation post.

Configuring session timeouts

Some functionality may be rolled out in phases and not immediately available in all regions.

April 14, 2026

Trigger data quality refresh for a data product

You can now trigger a full data quality refresh for all datasets within a data product in a single action.

What’s available

This release introduces on-demand data quality refresh at the data product level:

• One-click quality compute: Users with the appropriate permissions can trigger a data quality compute across all underlying datasets of a data product directly from the data product view. This runs validation rules and semantic type checks across all datasets at once, without needing to act on each dataset individually.

Why this matters

Data quality results can become stale as source data evolves. This update gives data product owners and quality leads a fast, centralized way to ensure quality scores and validation results reflect the latest data.

Computing data quality for data products

Some functionality may be rolled out in phases and not immediately available in all regions.