The following connectors will be removed and are no longer recommended for further use: Slack V2andFacebook Insightsfor Qlik Cloud Analytics Slack V2andFacebook Insightsfor Qlik Sense Enterprise on Windows Slack V2andFacebook Insightsfor the standalone Qlik Web Connector This change is driven by Slack’s updated app guidelines and requirements, which now classify exporting message data as unsuitable for external applications. The Qlik Automation and Qlik Talend CloudSlack connectors are unaffected. The Facebook Insights connector will be deprecated at the same time. When will the connectors be deprecated? The removal timeline is as follows: Qlik Cloud Analytics: End of July 2026 Qlik Web Connector (standalone): July 2026 release Qlik Sense Enterprise on Windows: November 2026 release If you have any questions, do not hesitate to contact us through the Qlik Customer Portal. Thank you for choosing Qlik,Qlik Support ...View More

Hello Qlik Sense Admins! Are you looking for best practices on how to manage and maintain your Qlik Sense client-managed environment? Then look no further than ourQlik Sense Admin Playbook, which is now available directly on Qlik Help. What is this playbook, and where can I find it? The playbook provides you witha repository of administrative best practices, organized by cadence and category for Qlik Sense Enterprise on Windows, and can be found here:Qlik Sense Admin Playbook It can also be accessed from the help site's top navigation bar > Playbooks (A) > Qlik Sense Administrator Playbook (B) : Do you collect feedback? Absolutely.To suggest improvements, please use theLeave your feedback hereoption on whichever page you want to comment on. What about the old playbook? Some of you may already be familiar with the playbook's previous iteration, and you will find that the old URL now redirects to the help site accordingly. The old content will be retired later in the year. Thank you for choosing Qlik,Qlik Support ...View More

Qlik constantly refines its Analytics, over time replacing old charts with new, modernized alternatives. These deprecations are announced well in advance and come with instructions on how to best replace these old charts, whether that is to use a new one, several new ones, or make use of new settings. This blog post covers the deprecation of charts in May 2027 and offers you guidance on how to replace them. What charts are being deprecated and when? The following seven visualization bundle charts are up for deprecation in May 2027. Most have already been removed from the asset panel and are no longer a part of recent applications. The Bar and Area chart The old Bullet chart The old Heatmap chart The Button for navigation The Share button The Show/Hide container The old Tabbed container The Multi KPI What do I use instead? Since these are old charts, most are no longer in use. If you happen to still have a very old application and need to replace deprecated charts, see Visualization bundle > Deprecated charts for more information on what to use instead. How do I find out if my apps are using the deprecated charts? Qlik recommends reviewing your apps for old charts. Depending on your platform (Qlik Cloud or Client-managed), there are different methods you can deploy. Qlik Cloud Qlik Cloud administrators should use theQlik Cloud Monitoring Appsto track the usage. The App Analyzer has a sheet dedicated to where deprecated charts are being used on a tenant in Qlik Cloud. The App Analyzer is based on usage events rather than scanning every app. Use the App Analyzer to find which apps and sheets have charts that need to be updated to newer and more modern alternatives. The easiest way to install and update theQlik Cloud Monitoring Appsis to use the automation template. If you already have the App Analyzer, just remove the automation and install a new one to get the latest version of the App Analyzer.  Client-managed For client-managed installations, use theMonitoring apps. TheContent Monitor apphas a sheet for tracking deprecated charts. At reload, the Content Monitor app scans every app in the installation in order to list all applications and sheets that are using charts that are being deprecated. It also lists the installed extensions and their deprecation status. The Monitoring apps are bundled with the Qlik Analytics installation. The first version with the new sheet will be included in the May 2026 release. If you want to track usage in prior versions, the deprecated chart usage scanner will also be available on the product download page. Thank you for choosing Qlik, Qlik Support ...View More

Update March 4th, 2026: added link toHow to get Talend Management Console task schedules and pause and resume during a maintenance window using the APIarticle TalendCloudandTalend Management Consolewill undergo scheduled maintenance inMarch,April, andMay.This infrastructure modernization is a key step in unifying the Talend ecosystem with Qlik. The alignment paves the way for a more seamless experience across both platforms. Over the coming months, you will gain access to integrated features that bridge data integration and analytics, enabling unified governance and a streamlined management experience across your entire data lifecycle. The maintenance windows will occur per region, during off-peak hours, and are expected to have a maximum of 30 minutes of effective downtime. What is the expected impact? A full outage of Talend Cloud and Talend Management Console for a duration of up to 30 minutes within a preplanned 4-hour window. The following applications will not be accessible: Talend Management Console (TMC) Talend Data Stewardship (TDS) Talend Data Preparation (TDP) Talend Data Inventory (TDC) Talend Pipeline Designer (TPD) Talend API Designer and Tester Talend Studio Talend Cloud Engines In detail: Cloud engines will not be available, and running executions will be terminated. Talend Studio users may be disconnected from their session, and it will not be possible to open a new Talend Studio session except in local mode. Executions that are already in progress during the outage will terminate correctly except on cloud engines, but all tasks or plans scheduled to start during those periods will be skipped. Skipped executions will not be tagged as failed, since they were never started. For this reason, check the execution status of your tasks and plans to ensure that all important ones are not skipped, or start them manually if necessary. See What do I need to do to prepare?further down in this blog post. Static IP addresses for Cloud Engines corresponding to Disaster Recovery regions will change during maintenance. See What follow-up actions are required?further down in this blog post. What do I need to do prepare? Pause jobs and plans before the maintenance window so there are no ongoing executions during the planned timeframe. Resume them after maintenance completes. If not stopped or paused, they will likely be in an inconsistent state at the end of the maintenance window. This concerns all jobs and plans scheduled to start or run during the maintenance window. See Checking scheduled task runs against your maintenance timetable on how to identify these plans and jobs. Looking for information on how to identify, pause, and resume your tasks? See How to get Talend Management Console task schedules and pause and resume during a maintenance window using the API. What follow-up actions are required? After the maintenance window, check and monitor the execution status of tasks and plans, as well asthe status of your Remote Engines.Remote Engines might require a restart if marked as unavailable in the Talend Management Console. If you use a predefined static IP on Cloud Engine, you will need to allow the new Disaster Recovery Region's IP addresses, which will have changed at this point. While this does not immediately affect production, it will impact any potential Disaster Recovery process.After the maintenance window, check your static IPs (Disaster Recovery) as documented in Using predefined static IP addresses for execution containers and update your firewalls accordingly.No change is required for the active region's IP addresses. They will be migrated and will work as of today, ensuring no production interruption. When will the maintenance take place? Each region will undergo maintenance for 4 hours during off-peak hours, with a maximum of 30 minutes of effective downtime. Region Maintenance Start Maintenance End Talend Cloud - AWS - Asia Pacific (Sydney)au.cloud.talend.com Wednesday 25 March 202622:00 AEDT (Sydney) UTC: 25/03/26 - 11:00 Thursday 26 March 202602:00 AEDT (Sydney) UTC:25/03/26 - 15:00 Talend Cloud - AWS - Asia Pacific (Tokyo)ap.cloud.talend.com Monday 20 April 202622:00 JST (Tokyo) UTC: 20/04/26 - 13:00 Tuesday 21 April 202602:00 JST (Tokyo) UTC:20/04/26 - 17:00 Talend Cloud - AWS - US East (N. Virginia)us.cloud.talend.com Monday 27 April 202602:00 EDT UTC: 27/04/26 - 6:00 Monday 27 April 202606:00 EDT UTC:27/04/26 - 10:00 Talend Cloud - AWS - Europe (Frankfurt)eu.cloud.talend.com Tuesday 26 May 202621:00 CEST UTC: 26/05/26 - 19:00 Wednesday 27 May 202601:00 CEST UTC:26/05/26 - 23:00 To identify which region your tenant is affected by, cross-reference Accessing Talend Cloud applications. 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

Qlik Cloud will undergo scheduled maintenance in March 2026. We’re upgrading and scaling our infrastructure to deliver a faster, more reliable, and seamless experience for you. These improvements strengthen performance, enhance stability, and ensure our platform continues to grow with your needs. The maintenance windows will occur per region and are expected to last a maximum of 60 minutes. What is the expected impact? Qlik Cloud will undergo scheduled maintenance that includes two separate impacts: (1) Qlik Cloud – Identity Services (Limited to three Regions | 30 Minutes) Qlik Cloud will experience a functional degradation of 30 minutes, during which its Identity Services are impacted: Impacted Regions: Qlik Cloud – AWS – Asia Pacific (Mumbai) Qlik Cloud – AWS – Europe (Ireland) Qlik Cloud – AWS – US East (N. Virginia) During this time: No new tenants can be created Users cannot be managed, which includes: Creating or inviting new users Updating user profiles Assigning groups Changing roles and permissions Deactivating or deleting users Group Management is unavailable, which includes: Creating new groups Modifying group settings Adding or removing members Updating group roles Role and Permission management is unavailable, which includes: Creating or modifying custom roles Updating permission assignments Changing role settings No other impact is expected. Existing users can continue to log in and use their assigned Qlik Sense applications as normal. Automation and report features will continue to function without interruption. If the existing user’s IdP (Identity Provider) information has changed, they may not be able to log in during the maintenance window. You may see the errorBAD-GATEWAY, Invalid response from the upstream service. Modifying roles or permissions during the maintenance window leads to aFailed to update roleerror with the error codeIDENTITIES-10405. (2) Qlik Answers (Global Impact – 60 minutes) A full outage of Qlik Answers during the 60-minute maintenance window. Knowledge base indexing and any queries will fail to run. Impacted Regions: Qlik Cloud – AWS – Asia Pacific (Tokyo) Qlik Cloud – AWS – Asia Pacific (Sydney) Qlik Cloud – AWS – Asia Pacific (Singapore) Qlik Cloud – AWS – Asia Pacific (Mumbai) Qlik Cloud – AWS – Europe (Frankfurt) Qlik Cloud – AWS – Europe (London) Qlik Cloud – AWS – Europe (Ireland) Qlik Cloud – AWS – US East (N. Virginia) What do I need to do to prepare? Be informed about the upcoming maintenance and alert your userbase if needed. No direct action is required from your end in preparation. What follow-up actions are required? None. When will the maintenance take place? The following tables include the maintenance start time for each affected region. To reiterate, the Qlik Cloud identity services are affected for 30 minutes, while the Qlik Answers maintenance is planned to last 60 minutes. Region Maintenance Start Asia-Pacific (Tokyo)(ap-ne-1) Monday 9 March 202623:00 JST (Tokyo)UTC: 9/03/26 – 14:00 Asia-Pacific (Sydney)(ap-se-2) Thursday 12 March 202601:00 AEDT (Sydney)UTC: 11/03/26 – 14:00 Europe (Frankfurt)(eu-c-1) Monday 16 March 202621:00 CET (Frankfurt)UTC: 16/03/26 – 20:00 Asia-Pacific (Mumbai)(ap-s-1) Tuesday 17 March 202620:00 IST (Mumbai)UTC: 17/03/26 – 14:30 Europe (Ireland)(eu-w-1) Wednesday 18 March 202621:00 GMT (Ireland)UTC: 18/03/26 - 21:00 Europe (London)(eu-w-2) Monday 23 March 202621:00 GMT (London)UTC: 23/03/26 - 21:00 Asia-Pacific (Singapore)(ap-se-1) Tuesday 24 March 202622:00 SST (Singapore)UTC: 24/03/26 - 14:00 North America (N. Virginia)(us-e-1) Wednesday 26 March 202621:30 EDT (Virginia, US)UTC: 27/03/26 - 01:30 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

Hello Qlik Talend admins! We introduced a new Content Delivery Network (CDN) URLto support the Talend Management Console UI. This change was previously communicated in the product and can be found as an item in our release notes from R2026-01. Should you encounter the errorWe couldn't load the applicationwhen accessing your Talend Management Console, check with your network team to verify that the new CDN was added to any firewall exceptions. The change required: Allow https://cdn.cloud.talend.com Traffic Type: Client-side only The URL is fetched by the user's web browser. No changes are required for backend connectivity (Remote Engines and Clusters). For all the required allowlist URLs, seeAdding URLs to your proxy and firewall allowlist. A relevant support article is available at Qlik Talend Management Console Error loading: We couldn't load the application. If you have questions about this change, contact your CSM (Customer Success Manager) or the Support team. Thank you for choosing Qlik,Qlik Support ...View More

Today, the Data Alerts featureinQlik Cloud Analyticsretains a history of data that meetsthe alert condition indefinitely. An upcoming change will introduce an automated purge. For more information on Data Alerts, see Monitoring data with alerts. What will the new retention policy be? The retention records (seen in Data Alert history) of Data Alert executions will be purged after 90 days or after 10 records (if not within the 90-day window). Why is the retention policy changing? The Data Alert feature was not designed to support long-term retention of data sets outside the core Qlik Sense App, but to allow you to detect outliers and anomalies in your data using quick and timely alerts. In addition, this will align the Data Alerts history with other retention periods on the platform and help eliminate ambiguity. What do I need to do? Unless data alert history is required beyond the set period, no action is needed from your end. In a use case where you need additional history, use the public APIs to facilitate the availability of alert evaluations and associated data. The Data Alerts REST API can be used to perform any required backup and retention. For more information, see Data Alerts REST | qlik.dev. Key end points: List data alert tasks Get data alert task List data alert task executions Get data alert task execution evaluation When will the changes take effect? The change will be applied starting Monday, April 20th, 2026. During this week: The retention rules will be implemented History beyond the 90-day window will be purged while leaving the most recent executions untouched; this will allow reports relying on comparisons against the last evaluation to continue to work (see Comparing with the last evaluation of the alert). The purge will happen on a rolling basis. If you have any questions, we're happy to assist. Reply to this blog post or take your queries to our Support Chat. Thank you for choosing Qlik,Qlik Support ...View More

Analytics only deliver value when insight is trusted. And trust comes from understanding the data behind it; where it came from, how it’s defined, and whether it’s fit for use. Bringing trusted, AI-ready data products directly into Qlik Cloud Analytics Data Products for Analytics are now available in Qlik Cloud Analytics Premium and Enterprise and Qlik Sense Enterprise. With this release, you can turn your existing QVDs and datasets into governed, discoverable, and reusable data products, adding data quality, context, and ownership directly within your analytics environment. What this brings: Stronger foundation for analytics and AI Turn trusted data into trusted insight Find and reuse trusted data, faster Read more in our Innovation blog:Data Products for Analytics Now Available And once you're ready to get started, here's what you'll need: What’s New in Qlik Cloud | Qlik Help Working with data products | Qlik Help Maximizing Data Value in the Age of AI | White Paper From Digital Swamp to Strategic Asset: Taming QVD Chaos with a Data Product Mindset | Blog Thank you for choosing Qlik,Qlik Support ...View More

Xero has announced the deprecation of several Accounting API objects, effective 28th of April 2026. These changes will impact existing Qlik Talend Cloud and Qlik Stitch Xero connectors. What exactly is changing? The following objects will be deprecated by Xero: Employees This object will be fully removed There is no replacement object Data for the Employees table will no longer be available after deprecation For more information, seeEmployees (Deprecated) | developer.xerox.com Expense Claimsand Receipts Xero recommends using the Invoices object as a replacement Customers must enable the Invoices table to continue receiving equivalent data For more information, seeExpense Claims (Deprecated) | developer.xerox.comandReceipts (Deprecated) | developer.xerox.com What action is Qlik taking? To support customers ahead of the deprecation date, Qlik plans two minor connector releases: 26 March 2026 This update introduced intentional failures designed to prompt you to take action before the endpoint is removed: Connections that have Employees, Expense Claims, or Receipts selected will begin to fail post-sync To minimize disruption and inbox noise, failures will occur no more than once per week per connection 27 April 2026 All references to the Employees, Expense Claims, and Receipts endpoints will be fully removed from the connector. From this date forward: Employees data will no longer be available Expense Claims and Receipts data will only be accessible via the Invoices table (if enabled) If you have any questions, we're happy to assist. Reply to this blog post or take your queries to our Support Chat. Thank you for choosing Qlik,Qlik Support ...View More

The patches resolving the post-upgrade ODBC-based connectors issue announced in this blog post have been released today. Check the download page for the following releases: Qlik Sense Enterprise on Windows November 2025Patch 3(Release Notes) Qlik Sense Enterprise on Windows May 2025Patch 13(Release Notes) Qlik Sense Enterprise on Windows November 2024Patch 25(Release Notes) For more information, seeUpgrade advisory for Qlik Sense on-premise November 2024 through November 2025: ODBC-based connectors. If you have any questions, we're happy to assist. Reply to this blog post or take your queries to our Support Chat. Thank you for choosing Qlik,Qlik Support ...View More