When we introduced enhanced self-service scheduling in April 2025, we removed the When data is refreshed option, which had let reload schedules trigger automatically when a dependent dataset was updated. At the time, we weren't able to carry that capability forward into the new task-based scheduler right away.
That capability is now returning. See What's New in Qlik Cloudand Scheduling data refreshes with tasks.
In the task editor, under Based on > Event, you can now select When data is refreshed to trigger a task automatically when a data update is detected in an upstream Qlik Talend Data Integration project that loads data into an analytics application.
The option is only available if the application is connected to a Qlik Talend Data Integration pipeline.
This brings back the event-driven automation the old scheduler offered, now built natively into the new self-service scheduling framework, with full compatibility with the multi-task model.
What does this mean for me?
If the application has an existing When data is refreshed schedule, this button might instead say Migrate. For applications with these schedules, clicking Migrate or Save will migrate all associated schedules to be individual tasks attached to the application.
No other action is required.
We're happy to assist with any follow-up questions. Reply to this blog post or take your queries to our Support Chat.
Thank you for choosing Qlik,Qlik Support
...View More
Our recently launched Public Previews give you early, hands-on access to what's coming next in Qlik Cloud, before the previewed features are generally available. Try new capabilities, shape their direction with your feedback, and stay ahead of the latest features.
Public Previews are enabled by default for most users and are directly accessible from your profile:
A tenant admin needs to activate the feature preview program.
Read all about it in Introducing feature previews (Innovation Blog).
The Highlights
Shape the roadmap: Share your feedback directly in the product and inform how Qlik Cloud evolves.
Stay up to date:Join Public Previewson Qlik Community, where our product team will advertise the available preview features.
You control your experience:Turn your personal preview experience on or off at any time - and as a tenant admin, manage who has access to the previews through a custom role.
Ready to know more?
Getting started is quick and easy. Here is all you need:
Public Previews | Qlik Community
Introducing feature previews
Managing feature preview for your tenant
What's New | Qlik Help
Thank you for choosing Qlik,Qlik Support
...View More
Effective in the Qlik Sense Enterprise on Windows November 2026 release, and in the latest patches for May 2025, November 2025, and May 2026, the ODBC connector used by Qlik Sense Enterprise on Windows will no longer support connections secured with TLS 1.0 or TLS 1.1. To maintain uninterrupted connectivity, customers should upgrade their environments to use TLS 1.2 or higher ahead of applying these releases or patches.
Refer to the release notes upon release of the affected versions for details.
Why is this happening?
TLS 1.0 and TLS 1.1 are legacy encryption protocols that are no longer considered secure and have been deprecated across the industry for several years. Removing support for these older protocols in the ODBC connector aligns Qlik's connectivity stack with current security standards and reduces exposure to known vulnerabilities in outdated TLS implementations.
Who is affected?
This change affects the ODBC connector in Qlik Sense Enterprise on Windows only. At this point, Qlik Sense Desktop and QlikView are not affected by this change.
Any data source connection made through the ODBC connector in Qlik Sense Enterprise on Windows that relies on TLS 1.0 or TLS 1.1 will be affected once support is removed, regardless of whether the TLS version is enforced by the data source itself, a network intermediary, or the client driver configuration.
What does this mean for me?
If your data source, ODBC driver, or the underlying operating system is currently configured to negotiate connections using only TLS 1.0 or TLS 1.1, those connections will fail once you move to a version of Qlik Sense Enterprise on Windows that removes TLS 1.0 or TLS 1.1 support.
Reload tasks, extensions, and any other workflows using affected ODBC connections will no longer be able to connect to the data source.
What should I do?
Review and upgrade your environment so that all ODBC connections negotiate TLS 1.2 or greaterbeforeyou upgrade Qlik Sense Enterprise on Windows.
If you are not already using TLS 1.2 or later, recreate the connection with the updated TLS configuration.
Questions?
If you have questions or need assistance planning your upgrade, our forums are open to you, and Support is only a chat away.
Thank you for choosing Qlik,Qlik Support
...View More
Don't miss our previous Q&A with Qlik! Pull up a chair and chat with our panel of experts to help you get the most out of your Qlik experience.
Let our Qlik experts offer creative solutions to your analytics demands and answer your visualization questions.
WATCH HERE
...View More
As Qlik moves to further modernize its existing product line, the following legacy QlikView components will be deprecated and are no longer included in the upcoming QlikView September 2026 release:
QlikView OCX: The QlikView OCX Component will no longer be maintained, and no further releases will be made available as of the September 2026 release.
QlikView IE Plugin for Cloud:While connecting to QlikView documents in Qlik Cloud will continue to function as expected with previous IE Plugins for Cloud, no new versions of the client will be released.
The IE Plugin for On-Premise installations will remain supported and willbe included in the September 2026 release.
QlikView Source Control: Connecting QlikView Desktop to a Source Control system will no longer be supported or updated as of the September 2026 release.
QlikView WorkBench: QlikView Workbench, used in Visual Studio to build QlikView integrations, will no longer be supported or updated as of the September 2026 release.
What about previous versions?
Older supported releases of the listed features (such as QlikView September 2025) remain fully operational and will be maintained in accordance withQlik's Release Management Policy.
We're happy to assist with any follow-up questions. Reply to this blog post or take your queries to our Support Chat.
And if you're ready to migrate to Qlik Cloud, get started with Migrating from QlikView, or contact your Qlik account team to arrange a more hands-on consultation.
Thank you for choosing Qlik,Qlik Support
...View More
Initial Publication:August 4,2026EditAugust 5, 19:10 UTC: Impact section updated.EditAugust 6, 06:11 UTC: Formatting changes only.EditAugust 6, 06:35 UTC: Investigation concluded, removed banner.
Certainopen sourcepackages released by Qlik® have beenimpactedby an ongoing, industry-widenpmsupply chain compromise ("Shai-Hulud") affectingkeyv, cacheable, and related packages. As of this writing, the campaign has affected many organizations beyond Qlik, including over 440 unique packages and 2,200+ package versions across thenpmecosystem. A Qliknpmpublishing credential was harvested from an internal build system after it installed a package with a poisoned transitive dependency, and was used to publish unauthorized, malicious versions of several Qlik-ownedopen sourcepackages to the publicnpmregistry. Thisappears to bea consequence of the broader worm's automated spread across thenpmecosystem, rather than a targeted attack on Qlik. The investigation into full scope and impactremainsactive, and Qlik has taken active steps to mitigate the impact.
Impact
We have confirmed that no Qlik products, including Qlik Cloud, Talend Cloud, and our client-managed offerings, were impacted.
No compromised code was released into any Qlik product.
31 packages in the @qliknpmscope had malicious versions published to the registry, all published and detected within the same 10:46 to 10:53 UTC window on August 4, 2026:
Package
Version
@qlik/api
2.14.2
@qlik/browserslist-config
3.0.2
@qlik/carbon-core
2.1.1
@qlik/carboncopy
1.1.6
@qlik/design-tokens
1.3.13
@qlik/dts-bundler
2.0.3
@qlik/embed-react
2.5.3
@qlik/embed-runtime
1.6.4
@qlik/embed-svelte
1.1.4
@qlik/embed-web-components
1.7.3
@qlik/eslint-config
2.0.20
@qlik/eslint-config-base
0.1.1
@qlik/eslint-config-react
0.1.1
@qlik/eslint-config-svelte
0.1.1
@qlik/eslint-config-vue
0.1.1
@qlik/nebula-table-utils
2.6.9
@qlik/oxfmt-config
0.1.6
@qlik/oxlint-config
0.7.2
@qlik/prettier-config
1.0.3
@qlik/react-native-simple-grid
1.5.5
@qlik/runtime-module-loader
1.5.1
@qlik/sdk
0.28.1
@qlik/sprout-design-docs
1.0.2
@qlik/sprout-gesture
0.0.13
@qlik/sprout-icons
0.12.3
@qlik/sprout-react
6.45.3
@qlik/sprout-react-table
0.16.7
@qlik/tsconfig
1.0.3
qlik-chart-modules
1.1.1
qlik-modifiers
0.10.1
qlik-object-conversion
0.17.2
What Qlik has done
Revoked the compromisednpmpublishing credential and disabled automated publishing pipelines (GitHub Actions), including across theqlik-ossorganization
Confirmed thatnpmremoved the malicious versions from the public registry; purging internal mirrors/caches
Added precautionary blocks on our cloud firewalls
Rotating exposed secrets and keys, in a controlled sequence, after confirming affected hosts are clean
Completed indicator-of-compromise sweeps across related GitHub organizations; no indicators of persistence found
Continuing a full investigation across our repositories and build infrastructure
What you should do
If you installed any of the affected package versions listed above:
Treat anynpm, GitHub, or cloud credentials present in that environment as potentially compromised
Scan for compromise before rotating credentials; do not rotate first
Reinstall using npm install --ignore-scripts once a clean version is confirmed available
More information
For independent tracking of the scale of this campaign across the npm ecosystem, see Socket's write-up: keyv and cacheable compromise.
...View More
Effective August 6th, 2026, the following breakdowns need to be enabled for Ad Accountsusing the Stitch Facebook Ads connector:
breakdowns=impression_device (and any combination including impression_device)
breakdowns=hourly_stats_aggregated_by_audience_time_zone
breakdowns=frequency_value
This change is driven by Facebook. For details, see Ads Insights API -- Breakdown Availability Changes | developers.facebook.com.
Thank you for choosing Qlik,Qlik Support
...View More
Qlik Cloud tenants hosted in the Europe (Ireland) region will undergo scheduled maintenance in August 2026 to upgrade the database supporting the underlying authentication service. The upgrade strengthens our ability to deliver a secure and reliable experience.
The maintenance window is expected to last 30 minutes.
Other regions are unaffected.
What is the expected impact?
If you are already signed in: You can continue working as usual.
If you need to sign out or sign in:Logging in and out are temporarily unavailable during the maintenance window. If you attempt to do so, you may encounter the following message:
{"errors":[{"title":"Unexpected server error","code":"UNEXPECTED","status":"500"}]}
This is expected and does not indicate a problem with your account.
What do I need to do to prepare?
No action is required.
What follow-up actions are required?
None.
When will the maintenance take place?
The maintenance is scheduled for:
Region
Maintenance Start
Maintenance End
Europe (Ireland)(eu-w-1)
Wednesday 12 August 202621:30 IST (Ireland)UTC: 12/08/26 – 20:30
Wednesday 12 August 202622:00 IST (Ireland)UTC: 12/08/26 – 21:00
To track further updates during the scheduled Qlik Cloud Maintenance, please visit our Qlik Cloud Status page. This blog post will be updated with additional information where necessary.
Thank you for choosing Qlik,Qlik Support
...View More
At the beginning of 2026, the Qlik Reporting Service expanded its offering with support for Microsoft Word and Microsoft PowerPoint report capabilities. For the duration of the first half of the year, these report formats have been executing in an unmetered state.
As of August 1st, 2026, these report formats will be metered. Customers using Word and PowerPoint reports will notice an increase in the report execution metrics.
What does this mean for me?
If you are a customer making use of these report formats, you should review your consumption and ensure that your Qlik Reporting Service quota is adequate for your aggregate report consumption at this time.
How do I know how many Word and PowerPoint reports are being sent?
Talk to your report developers, they would have a good understanding of which report task are in production and how many reports are being executed
For an aggregate view across your tenant, use the Report Analyzer appas perQlik Cloud Monitoring Apps Workflow Guide
Thank you for choosing Qlik,Qlik Support
...View More
