Qlik Cloud Governmentand Qlik Cloud Government DoDwill undergo a scheduled system upgrade impactingAutomationsand Backend Databases during the first half of September 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 US ET. Region Maintenance Window Qlik Cloud Government Sept 2 5PM ET - No Downtime Qlik Cloud Government DoD Sept 2 5PM ET - No Downtime Qlik Cloud Government Sept 8 5PM ET - No Downtime Qlik Cloud Government DoD Sept 8 5PM ET - No Downtime Qlik Cloud Government Sept 9 5pm ET - 1 Hour Downtime (Automations) Qlik Cloud Government DoD Sept 10 5pm ET - 1 Hour Downtime (Automations) 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 theQlik Cloud Status page. If you encounter unexpected complications during or after the maintenance, contactour Qlik Cloud Government Support inbox: government.support@qlikcloudgov.com. We will be happy to assist you. 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 from August look at Migrating to Qlik Cloud Analytics. 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 covered: Demonstration of the Qlik Cloud Analytics Migration tool Advantages of Qlik Cloud SaaS Readiness Click on this link watch ...View More

Hello Qlik Automate administrators and users, Based on feedback, Qlik has changed the wayerrors are handledin theQlik Reportingconnector forQlik Automate. The change was rolled out onAugust 12th,2025. The following blocks will be replaced to facilitate the changes: Get Chart Image Get Pixel Perfect Report Get Tabular Report The functional change of the new blocks centers on error handling. While the old blocks output a simplefailedstring in case of an error, we wanted to update this output to include the full error object, including the status code and reason. Additionally, in certain situations, the old blocks would have a successful run even though the output is an error; we updated this behavior so the new blocks will error out in any situation involving an error. What does this mean for me? The old blocks were renamed, flagging them as deprecated. Example: Get Chart Image (deprecated) The new blocks retain the old names and are referenced in the description of the old blocks. The action needed by Qlik Automate administrators and users is to switch from the (deprecated)blocks to the new ones. If you have any questions, we're happy to assist. Reply to this blog post or take similar queries to theQlik Application Automation forum.   Thank you for choosing Qlik,Qlik Support ...View More

Hello Qlik Automate admins and users, Previously, it was possible for Analytics Admin to move an existing automation connection to another user’s personal space. This behavior has been deprecated as personal spaces are meant to be private and exclusively managed by the space owner or Tenant Administrators. What does that mean for me? No action is required from your end. When will this change be implemented? The change was implemented today, on August 7th, 2025. If you have any questions, we're happy to assist. Reply to this blog post or take similar queries to theQlik Automate forum.   Thank you for choosing Qlik,Qlik Support ...View More

Hello Stitch Admins, Stitch has released a new version of itsGoogle Ads integration. With this release comes an update toGoogle Ads V2, which utilizes the latest Google Ads API (version 20). The previously used Google Ads API version 18 will be sunset by Google on August 20th, 2025. Once the API is sunset, integrations that interact with it will stop working. What do I need to do? Create a new integration to stay ahead of Google sunsetting version 18. We've put together a general guide to assist you. Using a new schema name If you are creating a new integration and don't plan on reusing the previous schema name, you can go ahead and make a new Google Ads integration. Selecting Google Ads from the integration options will default to the latest version, in this case, V2. The new integration will also benefit from the 7-day free historic sync. Re-using the schema name If you need to use the same schema name for the new integration, you must do the following: Pause the existing integration(s) in your Stitch account. Wait for any records that are being prepared to finish loading (such as waiting for Preparing to reflect 0 rows in the integration summary page). Take note of the tables and fields tracked for replication, as well as the replication methods defined for these tables. Delete the existing integration from your Stitch account. Drop or rename the existing schema from your destination data warehouse. We recommendrenaming the schema to preserve the data and maintain flexibility to adjust downstream workflows. Contact Qlik Support to coordinate a manual row-usage exemption for this integration. Configure a new integration with the same name, and Stitch will create this schema in your destination during the loading process. Frequently Asked Questions Q: Can I copy over my bookmarks to the new integration?A: Bookmarks cannot be covered over. When you create a new integration, every table will perform a full table replication from the start date set in the settings. Once the historic sync is complete, it will move to the selected replication method. There is no mechanism to manually set bookmarks, and individual integrations have no interaction with each other, even in upgrades. Q: What if I need more than 7 days to complete the historic sync?A: Reach out to Qlik Support for a manual exemption. Please explain why you need more time, and we will accommodate accordingly. Q: Will the data structure be the same in the new integration?A: We cannot guarantee the data structure is the same as it is determined by Google Ads API. If you are looking for field or table changes, please reference the Google Ads API comparison guides (Upgrade from v18 to v19 and Upgrade from v19 to v20). If you are missing data, reference Google's documentation to confirm it hasn't moved or been removed. In the event Google says data should exist, but it is not replicated, raise a ticket to Qlik Support to review and investigate. If you have any questions, we're happy to assist. Contact Support, reply to this blog post, or take similar queries to the Stitch forum. And if you want to stay up to date for Stitch-specific Support Updates, don't forget to subscribe!   Thank you for choosing Qlik,Qlik Support ...View More

Hello Qlik admins and developers, Previously, the Dropbox API used only long-lived access tokens. These long-lived access tokens have been deprecated since the fall of 2022, and only short-lived access tokens are created. Long-lived tokens remain usable for existing authentications. The Qlik Dropbox connectors have maintained the use of long-lived access tokens, and it is now time to deprecate these tokens and remove them. We aimto end support for long-lived tokens by October 31, 2025. What action do I need to take? Re-authenticate to avoid interruption. You will not have to take action for connection definitions created in Qlik products released from 2023 and onwards, and which were created or re-authenticated after 2022. This is applicable tothe following scenarios: Qlik Sense: Client Managed and Qlik Cloud Dropbox file location connector Dropbox Metadata connector Qlik Web Connector Standalone Qlik Dropbox Connector If you are using a long-lived access token in a Dropbox connection definition, you must follow the steps below to re-authenticate. This can be done proactively at any time, which will avoid the connections from breaking. What if I do not re-authenticate in time? Your connections will stop working once the long-lived access token expires. You can still re-authenticate in the same way at a later time; your connection will be repaired, and your reloads will work again. Is there some way for me to identify the connections? Unfortunately, there is no indication showing which type of token is used. However, if you are not sure when the connection was created or last re-authenticated, there is no harm in re-authenticating, regardless of whether it is necessary or not. How to re-authenticate in Qlik Sense: Client Managed and Qlik Cloud To re-authenticate the Dropbox connectors in Qlik Sense, update the connection within the Data load editor, then select Authenticate and follow the on-screen process to retrieve a new Authentication Code. Verify and Savethe connection when done. How to re-authenticate the Qlik Web Connector: Standalone Re-authenticate via the CanAuthenticate table by selecting to Clear the current Authentication Token, and then Authenticate to get a new Authentication Token. Save and Runwhen done. Additional recommendations While performing this review of your Dropbox connection definitions, it may also be an opportunity to remove any redundant connection definitions not in use. If you have any questions, we're happy to assist. Reply to this blog post or start a chat with us. Thank you for choosing Qlik,Qlik Support ...View More

Hello Qlik Automate users and admins, A series of changes have been identified across various GitLab APIs due to the deprecation of specific fields. For more information, seeREST API deprecations(docs.gitlab.com). As of the release of this post, GitLab has no official release date for API v5, and development has not yet started as of version 18.0. What will be changed? merged_by:In the Merge Request API, the merged_by field has been deprecated and replaced with merge_user. The following block response will be affected: List merge request Get merge request List updated merge request incrementally List new merge request incrementally merge_status:The merge_status field in the Merge Request API is deprecated and replaced with detailed_merge_status. The following block response will be affected: List merge request Get merge request Create merge request List updated merge request incrementally List new merge request incrementally default_branch_protection: The default_branch_protection field will be replaced with the default_branch_protection_defaults field. For more information, see default_branch_protection API field (docs.gitlab.com). The following block response will be affected: List groups Additional details on Response Changes Below you will find examples of responses with the deprecated (red) and new (green) fields. merged_by & merge_status fields [{"id": 1,"iid": 1,"project_id": 3,"title": "test1","description": "fixed login page css paddings","state": "merged","imported": false,"imported_from": "none","merged_by": {"id": --,"name": "--","username": "--","state": "active","avatar_url": "https://gitlab.example.com/--","web_url": "https://gitlab.com/--"},"merge_user": {"id": --,"name": "--","username": "--","state": "active","avatar_url": "https://gitlab.example.com/--","web_url": "https://gitlab.com/--"},"merged_at": "2018-09-07T11:16:17.520Z","merge_after": "2018-09-07T11:16:00.000Z","merge_when_pipeline_succeeds": true,"merge_status": "can_be_merged","detailed_merge_status": "not_open"}] default_branch_protection {"id": 96,"web_url": "https://gitlab.example.com/--","name": "test-1","path": "test-1","description": "","math_rendering_limits_enabled": true,"lock_math_rendering_limits_enabled": false,"default_branch": null,"default_branch_protection": 2,"default_branch_protection_defaults": {"allowed_to_push": [{"access_level": 40}],"allow_force_push": false,"allowed_to_merge": [{"access_level": 40}],"developer_can_initial_push": false},"avatar_url": null} What action do I need to take? All the above blocks referencing these deprecated fields in the other block should be updated with the new fields. 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

Hello Qlik Users, The newStraight Tablewas moved into the new native section of charts from the visualization bundle. The new Straight Table offers many improvements from the old table, and we encourage everyone to start using the new table instead of the old one. We've put together an article that aims to answer any frequently asked questions around this switch, beginning with: The old table will not be removed anytime soon. It will continue to work until further notice. We encourage you to subscribe to theQlik Support BlogandWhat's Newin Qlik Cloudto stay ahead of updates. The old table will not be updated further. Use the new table to benefit from future improvements. We monitor your feedback and will improve the functionality of the new table. To read up on new features, as well as how to replace the old table, head over to The new Straight Table and old Table (retired) in Qlik Analytics. Questions? We're only a comment or a chat away. Thank you for choosing Qlik,Qlik Support ...View More

Don't miss our latest 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

Hello Qlik Talend admins, Qlik is updating the Qlik Talend Nexus repository. The changes will be rolled out in a phased approach. The first phase will be deployed onJuly 16th,2025, from 1 AM to 4 AM GMT. The second phase will be rolled out later this year, with information on when and the expected impact to be published closer to the date. No estimated time is available yet. What is the expected impact? The impact is minimal. Qlik Talend Studio: Versions 7.2 to 8.0: No impact Versions 6.0.0 to 7.1.1: JAR files may no longer automatically download from Nexus Qlik Talend Administration Center No impact For more information on how to handle missing JAR files, see Update to Qlik Talend Nexus repository: downloading and installing missing JARs. If you have any questions, we're happy to assist. Reply to this blog post or start a chat with us. Thank you for choosing Qlik,Qlik Support ...View More