Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Qlik offers a wide range of channels to assist you in troubleshooting, answering frequently asked questions, and getting in touch with our technical experts. In this article, we guide you through all available avenues to secure your best possible experience.
For details on our terms and conditions, review the Qlik Support Policy.
Index:
We're happy to help! Here's a breakdown of resources for each type of need.
| Support | Professional Services (*) | |
| Reactively fixes technical issues as well as answers narrowly defined specific questions. Handles administrative issues to keep the product up-to-date and functioning. | Proactively accelerates projects, reduces risk, and achieves optimal configurations. Delivers expert help for training, planning, implementation, and performance improvement. | |
|
|
(*) reach out to your Account Manager or Customer Success Manager
Your first line of support: https://community.qlik.com/
Looking for content? Type your question into our global search bar:
Leverage the enhanced and continuously updated Knowledge Base to find solutions to your questions and best practice guides. Bookmark this page for quick access!
Subscribe to maximize your Qlik experience!
The Support Updates Blog
The Support Updates blog delivers important and useful Qlik Support information about end-of-product support, new service releases, and general support topics. (click)
The Qlik Design Blog
The Design blog is all about product and Qlik solutions, such as scripting, data modelling, visual design, extensions, best practices, and more! (click)
The Product Innovation Blog
By reading the Product Innovation blog, you will learn about what's new across all of the products in our growing Qlik product portfolio. (click)
Q&A with Qlik
Live sessions with Qlik Experts in which we focus on your questions.
Techspert Talks
Techspert Talks is a free webinar to facilitate knowledge sharing held on a monthly basis.
Technical Adoption Workshops
Our in depth, hands-on workshops allow new Qlik Cloud Admins to build alongside Qlik Experts.
Qlik Fix
Qlik Fix is a series of short video with helpful solutions for Qlik customers and partners.
Suggest an idea, and influence the next generation of Qlik features!
Search & Submit Ideas
Ideation Guidelines
Get the full value of the community.
Register a Qlik ID:
Incidents are supported through our Chat, by clicking Chat Now on any Support Page across Qlik Community.
To raise a new issue, all you need to do is chat with us. With this, we can:
Log in to manage and track your active cases in the Case Portal. (click)
Please note: to create a new case, it is easiest to do so via our chat (see above). Our chat will log your case through a series of guided intake questions.
When creating a case, you will be prompted to enter problem type and issue level. Definitions shared below:
Select Account Related for issues with your account, licenses, downloads, or payment.
Select Product Related for technical issues with Qlik products and platforms.
If your issue is account related, you will be asked to select a Priority level:
Select Medium/Low if the system is accessible, but there are some functional limitations that are not critical in the daily operation.
Select High if there are significant impacts on normal work or performance.
Select Urgent if there are major impacts on business-critical work or performance.
If your issue is product related, you will be asked to select a Severity level:
Severity 1: Qlik production software is down or not available, but not because of scheduled maintenance and/or upgrades.
Severity 2: Major functionality is not working in accordance with the technical specifications in documentation or significant performance degradation is experienced so that critical business operations cannot be performed.
Severity 3: Any error that is not Severity 1 Error or Severity 2 Issue. For more information, visit our Qlik Support Policy.
If you require a support case escalation, you have two options:
When other Support Channels are down for maintenance, please contact us via phone for high severity production-down concerns.
A collection of useful links.
Qlik Cloud Status Page
Keep up to date with Qlik Cloud's status.
Support Policy
Review our Service Level Agreements and License Agreements.
Live Chat and Case Portal
Your one stop to contact us.
After upgrading to Qlik Sense Enterprise on Windows May 2023 (or later), the Qlik Sense Repository Service may cause CPU usage spikes on the central node. In addition, the central Engine node may show an increased average RAM consumption while a high volume of reloads is being executed.
The Qlik Sense System_Repository log file will read:
"API call to Engine service was successful: The retrieved 'StaticByteSize' value for app 'App-GUID' is: 'Size in bytes' bytes."
Default location of log: C:\ProgramData\Qlik\Sense\Log\Repository\Trace\[Server_Name]_System_Repository.txt
This activity is associated with the ability to see the Base memory size in the Qlik Sense Enterprise Management Console. See Show base memory size of apps in QMC.
The feature to see Base memory size can be disabled. This may require an upgrade and will require downtime as configuration files need to be changed.
Take a backup of your environment before proceeding.
If any issues occur, revert the changes by restoring the backed up files and open a ticket with Support providing the changed versions of repository.exe.config, capabilities.json mentioning this article.
Show base memory size of apps in QMC
QB-22795
QB-24301
Qlik Sense Enterprise on Windows May 2023, August 2023, November 2023, February 2024.
This article aims to help you facilitate the most effective way to collaborate with Qlik Support. It defines your responsibilities as a partner, including reproducing issues, performing basic troubleshooting, and consulting the knowledge base or official documentation.
Before contacting Qlik Talend Technical Support, partners must complete the steps outlined in Qlik Responsible Partner Duties and should review the OEM/MSP Support Policy to understand the scope of support and the expectations on Partners.
Content
Identify which Qlik product, source endpoint, target endpoint, environment, or system layer is experiencing the issue.
For example, if a task fails in Qlik Replicate on Windows, check whether the issue occurs in a single task or across all tasks, whether it happens during full load or CDC, and whether it is related to a specific table or the data itself.
Similarly, if the issue occurs in only one environment (e.g., Production), ask the customer to confirm whether it can be reproduced in a test environment, or test in your own environment to determine if the issue is environment-related.
Always include the exact product name, version, source endpoint, target endpoint the customer is using.
Many issues are version-related, endpoint-related and Support cannot accurately investigate the issue without this information.
If the product the customer is using has reached End of life (EOL), please plan the upgrade. If the issue can be reproducible on the latest version, please reach out to us so that we can investigate and determine whether it's a defect or working as designed.
For End of Life or End of Support information, see Product Lifecycle
Partners are expected to recreate the customer’s environment (matching versions, configurations, and other relevant details) and attempt to reproduce the issue.
If you do not already have a test environment, please ensure one is set up. Having your own environment is essential for reproducing issues and confirming whether the same behavior occurs outside of the customer’s setup.
In some cases, it may also be helpful to test in a clean environment to rule out local configuration issues.
If the issue does not occur in the newer version or a clean setup, it may have already been resolved, and you can propose an upgrade as a solution.
See the Release Note for the resolved issues.
Regardless of whether the issue could be reproduced, please include:
While pasting a portion of the log into the case comment can help highlight the main error, it is still required to attach the Diagnostic Package with the entire original log file (using, for example, FileCloud).
Support requires the full verbose logs and task settings to understand the overall context and verify that the partial information provided is accurate and complete.
It is difficult to verify the root cause or provide reliable guidance without full verbose logs.
Additionally:
Please do not simply forward or copy and paste the customer’s inquiry.
As a responsible partner, you are expected to perform an initial investigation. In your case submission, clearly describe:
Sharing this thought process:
Even if the issue is still unresolved, outlining what you have already tried helps Support address it more quickly and effectively.
Attach all relevant files you have received from the customer and personally reviewed during your investigation, as well as all relevant files you have used when reproducing the steps.
Providing both the customer’s files and your reproduction files enables Support to verify whether the same issue occurs under the same conditions and to determine if the problem is reproducible, environment-specific, or specific to the customer’s configuration.
This includes (but is not limited to):
All support cases must be submitted using your official partner account, not the customer's account.
If you do not yet have a partner's account, contact Qlik Customer Support to request access and to receive the appropriate onboarding.
Review the support policy and set the case severity properly. See Qlik Support Policy and SLAs.
This template provides guidance on what to include and how to structure your case.
What happened? When did it happen? Where did it occur?
Clearly describe the issue, including:
Specify if applicable:
Find your Qlik Cloud Subscription ID and Tenant Hostname and ID
Only include what is needed based on the case type.
List the files you’ve included in the case and provide a brief description of each.
Summary of your Investigation
Explain what steps you took to investigate the issue before contacting Support.
Examples:
Thank you! We appreciate your cooperation in following these guidelines.
This ensures that your cases can be handled efficiently and escalated quickly when necessary.
The following release notes cover the Qlik PostgreSQL installer (QPI) version 1.2.0 to 2.1.0.
Content
| Improvement / Defect | Details |
| SHEND-2519 |
|
| QCB-32208 / SUPPORT-4028 |
|
| Improvement / Defect | Details |
| SHEND-2273 |
|
| QCB-28706 |
Upgraded PostgreSQL version to 14.17 to address the pg_dump vulnerability (CVE-2024-7348). |
| SUPPORT-335 | Upgraded PostgreSQL version to 14.17 to address the libcurl vulnerability (CVE-2024-7264). |
| QB-24990 | Fixed an issue with upgrades of PostgreSQL if Qlik Sense was installed in a custom directory, such as D:\Sense. |
| Improvement / Defect | Details |
| SHEND-1359, QB-15164: Add support for encoding special characters for Postgres password in QPI | If the super user password is set to have certain special characters, QPI did not allow upgrading PostgreSQL using this password. The workaround was to set a different password, use QPI to upgrade the PostgreSQL database and then reset the password after the upgrade. This workaround is not required anymore with 1.4.0 QPI, as 1.4.0 supports encoded passwords. |
| SHEND-1408: Qlik Sense services were not started again by QPI after the upgrade | QPI failed to restart Qlik services after upgrading the PostgreSQL database. This has been fixed now. |
| SHEND-1511: Upgrade not working from 9.6 database | In QPI 1.3.0, upgrade from PostgreSQL 9.6 version to 14.8 was failing. This issue is fixed in QPI 1.4.0 version. |
| QB-21082: Upgrade from May 23 Patch 3 to August 23 RC3 fails when QPI is used before attempting upgrade. QB-20581: May 2023 installer breaks QRS if QPI was used with a patch before. |
Using QPI on a patched Qlik Sense version caused issues in the earlier version. This is now supported. |
Qlik Sense Enterprise on Windows offers the ability to preload apps. See Creating preload tasks | help.qlik.com for details. This feature was introduced in the May 2024 release.
The app is automatically unloaded after the combined duration of the App cache time (engine setting) and Time to live (preload task). The timer starts after the app has last been used.
To set or verify App cache time:
To set or verify Time to live:
In the provided example, App cache time is set to 30 minutes and Time to live to 10 minutes. The app will unload after not being in use for 40 minutes.
The HubSection_Home resource filter in Qlik Sense refers to the button which allows a user to navigate back to the Hub from inside of an application.
Default ruleset:
If an administrator should want to disable this functionality for their users, for example, if the application is embedded into another page. Then they will want to disable the default rule named HubSections.
The result with this rule disabled is as follows for the end user:
The result of this change will disable this functionality for all users. If an administrator wants to provide this functionality to a select set of users then the administrator can create a new rule in this schema:
You may encounter an error : 400 - Invalid SNI when calling Talend Runtime API (Job as service) after installed 2025-02 patch or later. In the past before the patch version R2025-02 of Talend Runtime Server, it did work well when using the same certificate for SSL connection with Talend Runtime Server and did not cause any issue.
The SNI validation is active after 2025-02 patch or later.
There are three options to slove this issue
Disable SNI Host Check
This has the same security risk as jetty before it was updated (low security)
In <RuntimeInstallationFolder>/etc/org.ops4j.pax.web.cfg file, please add
jetty.ssl.sniRequired=false
and
jetty.ssl.sniHostCheck=false
Or configuring these jetty parameters in <RuntimeInstallationFolder>/etc/jetty.xml or jetty-ssl.xml file
<New id="sslHttpConfig" class="org.eclipse.jetty.server.HttpConfiguration">
<Arg><Ref refid="httpConfig"/></Arg>
<Call name="addCustomizer">
<Arg>
<New class="org.eclipse.jetty.server.SecureRequestCustomizer">
<Arg name="sniRequired" type="boolean">
<Property name="jetty.ssl.sniRequired" default="false"/>
</Arg>
<Arg name="sniHostCheck" type="boolean">
<Property name="jetty.ssl.sniHostCheck" default="false"/>
</Arg>
<Arg name="stsMaxAgeSeconds" type="int">
<Property name="jetty.ssl.stsMaxAgeSeconds" default="-1"/>
</Arg>
<Arg name="stsIncludeSubdomains" type="boolean">
<Property name="jetty.ssl.stsIncludeSubdomains" default="false"/>
</Arg>
</New>
</Arg>
</Call>
</New>
Resolve IP to Hostname
If the certification includes the domain name, you should use that domain name instead of the IP with the Jetty security updates in Talend Runtime Server.
But if your DNS server does not resolve the IP, you must call it by the IP address, so please check it at first to see if the workaround is feasible for your current situation.
In the examples the hostname is unresolvedhost.net and the IP is 10.20.30.40.
Try this API call at the command line:
curl -k -X GET --resolve unresolvedhost.net:9001:10.20.30.40 https://unresolvedhost.net:9001/services/
or
curl -k -X GET -H "Host: unresolvedhost.net" https://10.20.30.20:9001/services/
If this works, in your Talend component that makes the API call, go to "Advanced settings" or "Headers" table, add a row with Key: Host and Value: The hostname that matches your SSL certificate (e.g. unresolvedhost.net)
This will instruct Talend to send the correct Host header, which most HTTP clients (including Java's HttpClient) will also use as the SNI value during the TLS handshake.
The SNI enforcement is there for a security reason. With the 2025-02 patch, the Jetty components on Talend Runtime Server resolved a CVE security issue where they allowed a hostname to connect to a server that doesn't match the hostname in the server's TLS certificate.
Certificates require the URI not to be localhost or an IP address, and to have at least one dot, so a fully qualified domain name is best.
After configuring the Qlik Stitch user in Snowflake to use key-pair authentication and updating the Stitch destination settings accordingly, existing integrations begin to fail with the following error:
SQL access control error:
Insufficient privileges to operate on schema 'XXXX'.
Permissions are verified to be correct: All role grants and schema privileges are properly configured in Snowflake as documented in Connecting a Snowflake Destination to Stitch.
Switching back to password authentication restores the integrations, but does not satisfy security requirements for connecting to Snowflake.
Run the following SQL command in Snowflake:
ALTER USER STITCH_USER SET DEFAULT_ROLE = STITCH_ROLE;
This ensures the default role is automatically used when connecting via key-pair authentication.
If no role is explicitly defined during login, Snowflake will use STITCH_ROLE by default.
The issue might occur if Qlik Stitch is using outdated schema references or if the Stitch user’s privileges have changed after switching to key-pair authentication.
This article gives an overview of exporting the Qlik Sense apps from the source to a target shared space for backup purposes using Qlik Application Automation.
It explains a basic example of a template configured in Qlik Application Automation for this scenario.
You can make use of the template which is available in the template picker. You can find it by navigating to Add new -> New automation -> Search templates and searching for 'Export an app to a shared space as a backup' in the search bar and clicking on the Use template option in order to use it in the automation.
You will find a version of this automation attached to this article: "Export-app-to-shared-space.json". More information on importing automations can be found here.
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.
Export Qlik Sense Apps to GitHub
Running a Target Exec of a Qlik Talend Runtime (OSGi) build type artifact fails in Studio with the following:
Execution failed :java.lang.Exception: Job was not built successfully, please check the logs for more details available on C:/Talend/Talend8/Talend8Workspace/ESB2/poms/jobs/process/testmicroservice_0.1/lastGenerated.log
[Job was not built successfully, please check the logs for more details available on C:/Talend/Talend8/Talend8Workspace/ESB2/poms/jobs/process/testmicroservice_0.1/lastGenerated.log
The lastGenerated.log will contain messages similar to:
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.example.esb2.service:TestMicroservice:bundle:0.1.0
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.apache.commons:commons-lang3:jar -> version 3.10 vs 3.17.0 @ line 171, column 17
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
[WARNING] The requested profile "signature" could not be activated because it does not exist.
[INFO]
[INFO] -------------< org.example.esb2.service:TestMicroservice >--------------
[INFO] Building ESB2 TestMicroservice-0.1.0 (0.1,Job Designs) Bundle 0.1.0
[INFO] from pom.xml
[INFO] -------------------------------[ bundle ]-------------------------------
[INFO]
[INFO] --- osgihelper:8.0.11:generate (osgi-helper) @ TestMicroservice ---
[INFO] Resolve mvn:org.example.esb2.service/TestMicroservice/0.1.0
[INFO]
[INFO] --- resources:3.3.1:resources (default-resources) @ TestMicroservice ---
[INFO] Copying 2 resources from src\main\resources to target\classes
[INFO]
[INFO] --- compiler:3.11.0:compile (default-compile) @ TestMicroservice ---
[INFO] Not compiling main sources
[INFO]
[INFO] --- resources:3.3.1:testResources (default-testResources) @ TestMicroservice ---
[INFO] Not copying test resources
[INFO]
[INFO] --- compiler:3.11.0:testCompile (default-testCompile) @ TestMicroservice ---
[INFO] Not compiling test sources
[INFO]
[INFO] --- surefire:3.3.0:test (default-test) @ TestMicroservice ---
[INFO] Tests are skipped.
[INFO]
[INFO] --- bundle:6.0.0:bundle (default-bundle) @ TestMicroservice ---
[WARNING] Bundle org.example.esb2.service:TestMicroservice:bundle:0.1.0 : Invalid package name: '@BundleConfigExportPackage@' in Export-Package
[WARNING] Bundle org.example.esb2.service:TestMicroservice:bundle:0.1.0 : Invalid package name: '@BundleConfigImportPackage@' in Import-Package
[INFO] Building bundle: C:\Talend\Talend8\Talend8Workspace\ESB2\poms\jobs\process\testmicroservice_0.1\target\TestMicroservice-bundle-0.1.0.jar
[INFO] Writing manifest: C:\Talend\Talend8\Talend8Workspace\ESB2\poms\jobs\process\testmicroservice_0.1\target\classes\META-INF\MANIFEST.MF
[INFO]
[INFO] --- assembly:3.6.0:single (default) @ TestMicroservice ---
[INFO] Reading assembly descriptor: C:\Talend\Talend8\Talend8Workspace\ESB2\poms\jobs\process\testmicroservice_0.1/src/main/assemblies/assembly.xml
[WARNING] The following patterns were never triggered in this artifact inclusion filter:
o 'org.example.esb2.service:TestMicroservice:jar:0.1.0'
[INFO] Building jar: C:\Talend\Talend8\Talend8Workspace\ESB2\poms\jobs\process\testmicroservice_0.1\target\TestMicroservice-bundle-0.1.0.jar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4.650 s
[INFO] Finished at: 2025-10-23T09:12:57-04:00
[INFO] ------------------------------------------------------------------------
[WARNING] The requested profile "signature" could not be activated because it does not exist.
Change Build Type to Microservice.
The Remote Engine cannot run Talend Runtime (OSGi) build type artifacts. Therefore, Target Exec is not supported.
A Qlik Stitch Jira Integration encounters the following error during extraction:
500 JiraInternalServerError The server encountered an unexpected condition which prevented it from fulfilling the request.
...
CRITICAL HTTP-error-code: 500, Error: Internal server error
...
tap_jira.http.JiraInternalServerError: HTTP-error-code: 500, Error: Internal server error
Check Jira status page: https://status.atlassian.com/
If there are no active incidents and the error is recurring, please reach out to Jira Support and request to review the logs of your authorizing Jira account. The Jira Support team should be able to provide more insight into these occurrences. Jira Support can be reached at: https://support.atlassian.com/
In the event that they suggest Stitch needs to make specific accommodations, please reach out to Qlik Support and provide the details.
The Stitch Jira integration utilizes the JIRA Cloud REST API v2, which uses the standard HTTP status codes.
A 500 error generally indicates an issue with Jira's server(s). The integration has built-in retry logic to account for connection errors returned without an API response from Jira's server(s).
Ultimately, this error indicates that the Jira server was unable to complete our request. The 500 response is a raw error message from Jira that the extractions will capture in the logs.
A NetSuite Suite Analytics integration encounters the following error:
Failed to login using TBA
Qlik Stitch supports connecting to NetSuite2 (netsuite2.com) through token based authentication.
To use token based authentication, select the Use token based authenitcation option in your integration settings:
Note that this setting cannot be modified once the integration runs an extraction. If you are seeing this error in existing integration(s), you will need to create new ones with token based authentication selected.
For guidance on re-using schema names, see Qlik Stitch: How to Upgrade the Integration to Latest Version with Same Destination Schema.
NetSuite Suite Analytics has deprecated netsuite.com in favor of netsuite2.com. Token based authentication is required for a successful connection to netsuite2.com.
Due to a recent incident in the US-EAST-1 region, customer tenants may report inaccurate data movement capacities.
In certain conditions, the capacity for data movement tasks (Landing, Replication, and Lake Landing tasks) has been overreported. As a result, Qlik will not charge affected customers overage for the month of October 2025.
The incident only concerns the capacity metric (data moved) used for consumption and billing, and does not affect the operation of data movement or any other tasks.
No action is required by you to resolve the incident. Qlik is developing a fix to resolve telemetry data collection that will roll out in the coming weeks. The fix will resolve data movement capacity capture moving forward; however, historical telemetry data will not be adjusted.
During deployment of the fix, users may see data movement tasks briefly show as 'recoverable error' in the monitoring interfaces. This is a standard monitoring assertion built into Qlik Cloud that serves as a warning and does not impact the pipelines running in your gateway.
For any questions or concerns, please contact Qlik Support or your account representative
This article provides an overview of how to send straight table data to email as an HTML table using Qlik Automate.
The template is available on the template picker. You can find it by navigating to Add new -> New automation -> Search templates and searching for 'Send straight table data to email as table' in the search bar, and clicking the Use template option.
You will find a version of this automation attached to this article: "Send-straight-table-data-to-email -as-HTML-table.json".
Content:
The following steps describe how to build the demo automation:
An example output of the email sent:
The information in this article is provided as-is and will be used at your discretion. Depending on the tool(s) used, customization(s)andor other factors, ongoing support on the solution below may not be provided by Qlik Support.
How to export more than 100k cells using Get Straight Table Data Block
This article describes how an Excel file can be sent as an attachment by using the Send Mail block in Qlik Application Automation.
Automation Structure
The creation of an Excel report from a Qlik Sense straight table is explained in the first part of this article.
Let's walk through the blocks used in the automation workflow to send the Excel file as an attachment using the "Send Mail" block.
A JSON file containing the above automation is attached to this article.
Please follow the steps provided in the How to import automation from a JSON file article to import the automation.
This article describes how to handle dynamic tables in Qlik Replicate, such as when source tables are frequently added and deleted. This avoids having to manually add the table to a task each time.
The methods described will work for most source endpoints.
Our example uses Oracle as the source.
Create a new table in the source:
create table SYSTEM.suri4(id int primary key, anane varchar(10))
The client Secret for a Single Sign-On Solution has expired.
After successfully logging in with a recovery address (https:// YOUR-TENEANT .eu.qlikcloud.com/login/recover) using the Service Account Owner (SAO) account, logging in to the Qlik Cloud Administration Console fails with:
User allocation required You do not have a valid user allocation. Please contact an administrator for more information
Once you successfully log in to the tenant via recovery link using the SAO (Service Account Owner) credentials, either navigate to the Qlik Cloud Administration Console by using
This will allow you to access the Qlik Cloud Administration Console and update the client secret for your IDP settings.
Generating an API key fails with:
An error occurred when generating the API Key. Please try again.
The user does not have a role with the required permission.
The old Developer role will be deprecated. Follow the steps in this article to future proof your system and create a custom role.
This article explains how you can Delete spaces in Qlik Cloud Services using Qlik Automate. Multiple spaces can be deleted during one run. As when deleting a space via the user interface, this will also delete any apps, data files or other content within the space(s) using the relevant blocks for those content types.
For information about spaces in Qlik Cloud, see Navigating Spaces.
This automation is not designed to be triggered using a webhook or on a schedule. It has been designed with manual user input in mind and requires multiple confirmations.
If you use your own automation to delete spaces, know that deleting a space via the space blocks will not delete the content in the space, and will instead result in that content being orphaned in the tenant. Leverage the examples in this automation to first delete content from spaces prior to deleting the space.
Once deleted, spaces, apps, or data files cannot be recovered.
Content:
This automation assumes you have a TenantAdmin role.
The automation is divided into five sections:
The Start section retrieves all available spaces and prompts you to select what spaces you want to delete.
Overview:
Setting it up:
This section provides the possibility to review the selected spaces before deleting them.
Overview:
Setting it up:
Once deleted, spaces, apps, or data files cannot be recovered.
This section deletes all existing apps inside the space(s). A space cannot be removed before all apps are deleted.
Overview:
Setting it up:
Once deleted, spaces, apps, or data files cannot be recovered.
This section deletes all data files within the selected space(s).
Overview:
Setting it up:
Once deleted, spaces, apps, or data files cannot be recovered.
This section deletes all selected spaces.
Overview:
Setting it up:
This section wraps up the automation and updates the final status of the automation run.
Overview:
Setting it up:
Navigating Spaces
Managing permissions in shared spaces
Managing permissions in managed spaces
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.
Is it possible to upgrade windows server OS on the same machine where Qlik Sense, QlikView, or Qlik NPrinting are installed?
How will Windows Update and Windows Service packs affect Qlik Products?
Questions often arise when upgrading or applying Windows Service packs or running Windows Update, e.g. "Will applying service packs or patches from Microsoft affect installed Qlik software or clients?"
Typically upgrading Windows or applying patches or installing Window Service packs should not affect any installed Qlik products. As a precaution to prevent unexpected effects, below practices are recommended.
General best practices to prepare for updates include:
If you have general questions regarding compatibility of host operating systems, please review the release notes for your release. If you have questions regarding specific patches, raise this query directly in the relevant Qlik product forums.
Qlik Sense Enterprise Client-Managed offers a range of Monitoring Applications that come pre-installed with the product.
Qlik Cloud offers the Data Capacity Reporting App for customers on a capacity subscription, and additionally customers can opt to leverage the Qlik Cloud Monitoring apps.
This article provides information on available apps for each platform.
The Data Capacity Reporting App is a Qlik Sense application built for Qlik Cloud, which helps you to monitor the capacity consumption for your license at both a consolidated and a detailed level. It is available for deployment via the administration activity center in a tenant with a capacity subscription.
The Data Capacity Reporting App is a fully supported app distributed within the product. For more information, see Qlik Help.
The Access Evaluator is a Qlik Sense application built for Qlik Cloud, which helps you to analyze user roles, access, and permissions across a tenant.
The app provides:
For more information, see Qlik Cloud Access Evaluator.
The Answers Analyzer provides a comprehensive Qlik Sense dashboard to analyze Qlik Answers metadata across a Qlik Cloud tenant.
It provides the ability to:
For more information, see Qlik Cloud Answers Analyzer.
The App Analyzer is a Qlik Sense application built for Qlik Cloud, which helps you to analyze and monitor Qlik Sense applications in your tenant.
The app provides:
For more information, see Qlik Cloud App Analyzer.
The Automation Analyzer is a Qlik Sense application built for Qlik Cloud, which helps you to analyze and monitor Qlik Application Automation runs in your tenant.
Some of the benefits of this application are as follows:
For more information, see Qlik Cloud Automation Analyzer.
The Entitlement Analyzer is a Qlik Sense application built for Qlik Cloud, which provides Entitlement usage overview for your Qlik Cloud tenant for user-based subscriptions.
The app provides:
For more information, see The Entitlement Analyzer.
The Reload Analyzer is a Qlik Sense application built for Qlik Cloud, which provides an overview of data refreshes for your Qlik Cloud tenant.
The app provides:
For more information, see Qlik Cloud Reload Analyzer.
The Report Analyzer provides a comprehensive dashboard to analyze metered report metadata across a Qlik Cloud tenant.
The app provides:
For more information, see Qlik Cloud Report Analyzer.
Do you want to automate the installation, upgrade, and management of your Qlik Cloud Monitoring apps? With the Qlik Cloud Monitoring Apps Workflow, made possible through Qlik's Application Automation, you can:
For more information and usage instructions, see Qlik Cloud Monitoring Apps Workflow Guide.
The OEM Dashboard is a Qlik Sense application for Qlik Cloud designed for OEM partners to centrally monitor usage data across their customers’ tenants. It provides a single pane to review numerous dimensions and measures, compare trends, and quickly spot issues across many different areas.
Although this dashboard is designed for OEMs, it can also be used by partners and customers who manage more than one tenant in Qlik Cloud.
For more information and to download the app and usage instructions, see Qlik Cloud OEM Dashboard & Console Settings Collector.
With the exception of the Data Capacity Reporting App, all Qlik Cloud monitoring applications are provided as-is and are not supported by Qlik. Over time, the APIs and metrics used by the apps may change, so it is advised to monitor each repository for updates and to update the apps promptly when new versions are available.
If you have issues while using these apps, support is provided on a best-efforts basis by contributors to the repositories on GitHub.
The Operations Monitor loads service logs to populate charts covering performance history of hardware utilization, active users, app sessions, results of reload tasks, and errors and warnings. It also tracks changes made in the QMC that affect the Operations Monitor.
The License Monitor loads service logs to populate charts and tables covering token allocation, usage of login and user passes, and errors and warnings.
For a more detailed description of the sheets and visualizations in both apps, visit the story About the License Monitor or About the Operations Monitor that is available from the app overview page, under Stories.
Basic information can be found here:
The License Monitor
The Operations Monitor
Both apps come pre-installed with Qlik Sense.
If a direct download is required: Sense License Monitor | Sense Operations Monitor. Note that Support can only be provided for Apps pre-installed with your latest version of Qlik Sense Enterprise on Windows.
The App Metadata Analyzer app provides a dashboard to analyze Qlik Sense application metadata across your Qlik Sense Enterprise deployment. It gives you a holistic view of all your Qlik Sense apps, including granular level detail of an app's data model and its resource utilization.
Basic information can be found here:
App Metadata Analyzer (help.qlik.com)
For more details and best practices, see:
App Metadata Analyzer (Admin Playbook)
The app comes pre-installed with Qlik Sense.
Looking to discuss the Monitoring Applications? Here we share key versions of the Sense Monitor Apps and the latest QV Governance Dashboard as well as discuss best practices, post video tutorials, and ask questions.
LogAnalysis App: The Qlik Sense app for troubleshooting Qlik Sense Enterprise on Windows logs
Sessions Monitor, Reloads-Monitor, Log-Monitor
Connectors Log Analyzer
All Other Apps are provided as-is and no ongoing support will be provided by Qlik Support.