Qlik Cloud will undergo a scheduled system upgrade impacting Automations during the month of April 2025, to improve the continued stability and performance of our platform. Reloads, reports and other workloads referenced by automations may also be impacted during the maintenance window. When will I be impacted? This table lists all affected regions and their expected maintenance window. The times are listed in Central European Summer time and the local time relevant to the tenant. Region Maintenance Window (CEST) Local time Europe (Stockholm, Anonymous Access) April 16 3 PM – 4 PM CEST April 16 3 PM – 4 PM CEST Middle East (UAE) April 16 4 PM – 5 PM CEST April 16 6 PM – 7 PM GST Asia Pacific (Mumbai) April 17 3 PM – 4 PM CEST April 17 6.30 PM - 7.30 PM IST Asia Pacific (Tokyo) April 22 7 PM – 8 PM CEST April 23 2 AM – 3 AM JST Europe (London) April 23 5 AM – 6 AM CEST April 23 4 AM – 5 AM BST US East (N. Virginia) April 23 6 AM – 7 AM CEST April 23 12 AM – 1 AM EDT Asia Pacific (Singapore) April 23 7 PM – 8 PM CEST April 24 1 AM – 2 AM SGT Asia Pacific (Sydney) April 23 8 PM – 9 PM CEST April 24 4 AM – 5 AM AEST Europe (Frankfurt) April 24 5 AM – 6 AM CEST April 24 5 AM – 6 AM CEST Europe (Ireland) April 24 6 AM – 7 AM CEST April 24 5 AM – 6 AM IST How will I be impacted? During the scheduled maintenance window, all automations features will be impacted. In addition to the specific impact on automations as specified below, this will also impact reloads, reports and other workloads referenced by automations. In-product automation pages: The automation pages in the UI will be unavailable, and a service unavailable message will be displayed. Webhook Triggered Automations: Incoming webhooks from external platforms may be lost during maintenance and the calling system will receive a 429 status code in response. You can resend the internal Qlik Cloud webhooks after the maintenance period has passed from the webhooks page which is accessible from your Administration Console. Triggered Automations: Any triggered automations sent during the maintenance window will be lost, and a 429 status code will be returned in the response. This includes triggered automations from buttons, external third-party tools, or other use cases relying on this functionality. Scheduled Automations: Scheduled automations, including those that trigger reloads, reports, or other use cases, will not run during the maintenance window. However, they will automatically restart after the maintenance is completed. Automations API: The Automations API endpoints will be unavailable during the maintenance window. Disconnected OAuth app or webhook: In rare cases, too many 429 responses on a webhook or triggered request may cause the requesting system to disconnect the OAuth app or webhook (for webhook automations only), requiring manual reconnection. To reconnect a webhook, disable and re-enable the automation, which will recreate the webhook. We apologize for any inconvenience this may cause and appreciate your understanding as we work to improve the stability and performance of our platform. To track updates during the scheduled maintenance, please visit the Qlik Cloud Status page. If you encounter unexpected complications during or after the maintenance, contact Qlik Support using live chat. We will be happy to assist you. Thank you for choosing Qlik, Qlik Support ...View More

The Qlik Enterprise Manager connector for Qlik Application Automation is being effectively discontinued on April 28th of 2025. If you are looking for an alternative to the Qlik Enterprise Manager connector, Qlik offers generic connectors that can be used in conjunction with the Qlik Enterprise Manager API. For more information, see: Getting started with the generic connectivity in Qlik Application Automation Qlik Enterprise Manager API Guide 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

Multiple log-based replication issues may affect Qlik Replicate customers using SAP HANA DB 2.0 who are upgrading to the SAP HANA service packs SPS7 and SPS8. What problems have been identified? SAP HANA DB 2.0 SPS7 (Service Pack 7): RECOB-9379: SAP Hana Log-Based SPS7 (73 and 76) version date and timestamp columns replicating as NULL RECOB-9427: SAP HANA log-based task erroring when the log position was at the end of the transaction log RECOB-9379 and RECOB-9427 have been addressed by Qlik. An early build (Qlik Replicate 2024.11, SP03 Early Build) is available. Download the early build from: https://files.qlik.com/url/wucx4x2nbyytwseu (password: pk2pfzup) No other issues in Service Pack 7 are known. SAP HANA DB 2.0 SPS8 (Service Pack 8): RECOB-9652: There is still ongoing work in R&D related to DML operations failing to get data values in Hana Log Based SP08 (80 & 81). What action can be taken? Customers planning to upgrade to SPS7 or SPS8 should be aware of the risk, particularly with the changes to Hana logs affecting the Hana log parsing with respective to Qlik Replicate. We strongly advise postponing any upgrades to these versions until Qlik R&D has reviewed and certified these service packs. What about trigger-based replication? Qlik has not received any reports of customers using trigger-based replication experiencing the same issues. However, if an upgrade is planned, we recommend thoroughly testing in lower environments before scheduling any production upgrades. Thank you for choosing Qlik, Qlik Support ...View More

Hi everyone, Want to stay a step ahead of important Qlik support issues? Then sign up for our monthly webinar series where you can get first-hand insights from Qlik experts. The Techspert Talks session from April looked at Stitch Migration to Qlik Cloud. But wait, what is it exactly?Techspert Talks is a free webinar held on a monthly basis, where you can hear directly from Qlik Techsperts on topics that are relevant to Customers and Partners today. In this session we will cover: Understanding the schemas Demonstration of the migration process Best practices and tips for a smooth transition Click on this link to see the presentation ...View More

Hello, Qlik Replicate admins, Beginning inQ3 2025, Snowflake will mandate Multifactor Authentication (MFA). For detailed information and a timetable, see FAQ: Snowflake Will Block Single-Factor Password Authentication by November 2025. How will this affect Qlik Replicate? Unless MFA has been set up, this change will impact connectivity to Qlik Replicate. How do I prepare for the change? To mitigate the impact,switch to Key Pair Authentication. Key Pair Authentication is available by default starting with Qlik Replicate 2024.05. For more information, see Setting general connection parameters. If an upgrade is currently not feasible, reviewHow to setup Key Pair Authentication in Snowflake and How to configure this enhanced security mechanism in Qlik Replicatefor a possible workaround to apply Key Pair Authentication. If you have any questions, we're happy to assist. Reply to this blog post or take similar queries to theQlik Replicate forum.   Thank you for choosing Qlik,Qlik Support ...View More

Edit 31st of March 2025: AddedCVE number. Hello Qlik users, A security issue in a version of Qlik Alerting Windows has been identified. This issue was resolved in a later patch, which is already available. Details can be found in the Security Bulletin Critical Security fix for Qlik Alerting (CVE-2025-31509. The impacted Qlik Alerting Windows version isJuly 2023 SR1. No workarounds can be provided. Customers should upgrade toQlik Alerting July 2023 Service Release 2or higher. All Qlik software can be downloaded from our officialQlik Download page(customer login required). Follow best practices when upgrading Qlik Alerting. The information in this post and the Security Bulletin Critical Security fix for Qlik Alerting (CVE-2025-31509are disclosed in accordance with our published Security and Vulnerability Policy. The Security Notice label is used to notify customers about security patches and upgrades that require a customer’s action. Please subscribe to the ‘Security Notice’ label to be notified of future updates. Thank you for choosing Qlik,Qlik Global Support ...View More

The Qlik Application Automation JIRA blocks List issues, List issues by project and List new and updated issues incrementally, have been updated to the latest API URL. The changes come into effect on the 1st of May 2025. What has changed? The following changes in the blocks: Input Parameter changes  List issues block: Current (Old) Version:Input parameter "Jql"is optional New Version:Input parameter"Jql"is a required parameter List issues by project: Current (Old) Version:Input parameter "Project" is optional New Version:Input parameter "Project" is a required parameter List new and updated issues incrementally: No changes Response changes Old Response:By default, all navigable fields are returned.If a list of specific fields should be returned, specify the names of the fields in the "Fields" input parameter.For an example of the raw response, see the attached .json (JIRA-old-response.json) file. New Response:By default, the resource returns IDs only.If a list of specific fields should be returned other than “id”, specify the names of the fields in the "Fields" input parameter.Example of the response: [{"id": "157638"},{"id": "156647"}]   Example of the response if a user has specified the names of the field (such as "Summary") in the "Fields"input parameter: [{"expand": "","fields": {"summary": "Main order flow broken"},"id": "10002","key": "ED-1","self": "https://your-domain.atlassian.net/rest/api/3/issue/10002"}] How do I prepare for the change? Update your automations to use the new updated blocks:  Select the old block Then click Upgrade to latest versionFollow the same steps for all remaining blocks, such as List issues by project and List new and updated issues incrementally. Since the response has been updated, the "Id" field will be returned by default if no fields are specified in the "Fields" input parameter.After upgrading any of the List issues, List issues by project, and List new and updated issues incrementally blocks, add the relevant fields to the input parameter in the block, which is referenced by other blocks. Additionally, modify the output references in other blocks if necessary. If this is not done, it will result in a null value for the input parameter, causing referenced blocks to fail with the error "Missing mandatory parameter" whenever the input parameter is required.Example error:{ "response": { "status": 400, "body": { "errors": [ { "code": "HTTP-400", "title": "Invalid Request.", "detail": "Missing mandatory parameter \"Summary\"." } ] } }, "external error": false } If you have any questions, we're happy to assist. Reply to this blog post or take similar queries to the Qlik Application Automation forum.   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. SEE THE RECORDING HERE ...View More

The Qlik Application Automation HubSpot block Get Contact by Emailhas been updated to the latest API version, pointing it to HubSpot v3 API. What has changed? Input Parameterchanges The new version changes how input parameters are handled. While the current (old) block returns all properties by default, the new block requires explicitly specifying the fields you need. Input Parameters available in the old (current) block: Email Input Parameters available in the new block: Email Properties Properties With History Associations By default, it will only fetch data as shown in the example below. If additional details are required, input parameters like Properties, Properties With History, andAssociations must be added. Default example: {"id": "1","properties": {"createdate": "2021-07-27T13:13:25.669Z","email": "emailmaria@hubspot.com","firstname": "Marino","hs_object_id": "1","lastmodifieddate": "2023-07-27T23:18:09.664Z","lastname": "Johnson (Sample Contact)"},"createdAt": "2021-07-27T13:13:25.669Z","updatedAt": "2023-07-27T23:18:09.664Z","archived": false,"key_values": {"createdate": null,"email": null,"firstname": null,"hs_object_id": null,"lastmodifieddate": null,"lastname": null}} Response changes Top-Level Structure Differences: Old Response: Uses "vid" as the contact identifier. Contains "canonical-vid" and "merged-vids" for tracking multiple contact records. "portal-id" is included to indicate the HubSpot account. New Response: Uses "id" as the contact identifier instead of "vid". Omits "canonical-vid", "merged-vids", and "portal-id". Properties Structure: Old Response: Each property has "value" and "versions" fields to track changes over time. "versions" include timestamps, sources, and previous values. New Response: Properties are flattened, storing only the latest value under "properties". Historical values are now under "propertiesWithHistory", making the structure more modular. Timestamp Format: Old Response: Uses Unix timestamps (e.g., "1627391605669"). New Response: Uses ISO 8601 format (e.g., "2021-07-27T13:13:25.669Z"), making it more human-readable. Data Organization: Old Response: Mixes computed, user-set, and system-set fields within "properties", making it harder to distinguish sources. New Response: Separates historical data into "propertiesWithHistory", improving clarity. See the attached.JSONfiles for comparison responses between the old (hubspot-old-get-contact-by-email.json) and the new(hubspot-new-get-contact-by-email.json) block. How will this affect me? If you currently use the HubSpot connector'sGet Contact by Emailblock and do not upgrade it to the new version, the block will stop functioning onMay 30th, 2025. How do I prepare for the change? Update your automations to use the newGet Contact by Emailblock: Select the old block Then clickUpgrade to latest version Since the response has changed, modify the output reference in other blocks once you have upgraded the Get Contact by Emailblock. Failing to do so will lead to an input parameter with a null value and cause referenced blocks to fail with the error "Missing mandatory parameter" wherever the input parameter is mandatory.Example error: {"response": {"status": 400,"body": {"errors": [{"code": "HTTP-400","title": "Invalid Request.","detail": "Missing mandatory parameter \"id\"."}]}},"external error": false} If you have any questions, we're happy to assist. Reply to this blog post or take similar queries to the Qlik Application Automation forum. Thank you for choosing Qlik,Qlik Support ...View More

We are introducing a breaking change to the behavior of file paths returned by the DataFiles connector to Qlik Sense. This update is designed to align DataFiles with the web storage provider connectors. This will better align the DataFiles connector's behavior with other connectors, such as S3, which return folder names with a trailing slash for the DirList argument in loops. Other web storage provider connectors are not affected. What's changing Current Behavior When using the DirList function with the DataFiles connector, the returned folder path does not include a trailing slash. New Behavior With the upcoming update, the DirList function will now return folder paths with a trailing slash—matching the behavior of other storage connectors like S3. This change is part of our ongoing efforts to support file hierarchy enhancements introduced in Q4 2024 and to ensure consistency across all connectors. How does this impact your Qlik Sense load script? The change will primarily affect loops or code configurations that rely on the specific behavior of the output from aDirList argument when processing directory paths. Customers who have implemented custom filtering logic based on the absence of a trailing slash may need to adjust their scripts. Example script: // List out the response from DirList as DirFor Each Dir in DirList('lib://DataFiles/')ShowThePath:LOAD'$(Dir)' as PathAutoGenerate 1;Next; Before the fix, this will return: Path lib://DataFiles/directory1 lib://DataFiles/directory2 Post-fix, this will return: Path lib://DataFiles/directory1/ lib://DataFiles/directory2/ What scenarios are unaffected? Customers using other file listing or filepath functionsare not expected to experience any impact. Most standard code configurations remain unchanged. When will the change be rolled out? The update will be rolled out to all Qlik Cloud tenants onMarch 25th, 2025. Qlik Cloud Government tenants will receive the update byMarch 25th or later. Thank you for choosing Qlik,Qlik Support ...View More