Qlik product downloads are accessible through the Qlik Download page on Qlik Community, which embeds a Qlik Cloud app. However, while the Qlik Community presents the download experience, GitHub stores and serves the installer assets as the backend distribution platform.

As a result, download URLs do not use a qlik.com domain.

This article explains the download flow and practical allowlisting options, specifically for use cases requiring exceptions for download destinations in firewalls, proxies, or endpoint security tools.

Download Sequence

While the visible link is a GitHub URL, the file always downloads from a second, dynamically generated URL on a different host. This two-step redirect is standard GitHub behavior for release downloads, not something specific to Qlik, and you must account for it when you define allowlisting rules.

When you select a download link, the request follows a fixed sequence of steps before Qlik delivers the file:

1. The customer selects a Download Link on the Qlik Download page.
2. The link points to a human-friendly GitHub release download URL, in the form: https://github.com/qlik-download/<repo>/releases/download/<tag>/<filename>
3. The customer's browser sends a request to that GitHub URL.
4. GitHub returns an HTTP redirect, not the file, to a technical delivery URL hosted on release-assets.githubusercontent.com.
5. The redirect URL includes a repository identifier, an asset path, and a signed, time-limited query string that GitHub generates at request time. Because GitHub generates these values dynamically per request, and they expire after a short period, no one can know or predict the final redirect URL in advance.

   As a result, the Qlik Download page can't publish it as a static link, and can only link to the initial GitHub release URL. The redirect must happen at download time.

   The visible link is a GitHub URL, but the file always downloads from a second, dynamically generated URL on a different host. This two-step redirect is standard GitHub behavior for release downloads, not something specific to Qlik, and you must account for it when you define allowlisting rules.
6. Your browser follows the redirect automatically, and the installer file downloads from that final release-assets.githubusercontent.com URL.

Allowlisting Reference

The following table lists, per product, the stable GitHub download URL prefix and the corresponding redirect URL prefix on release-assets.githubusercontent.com. These prefixes are predictable, so you can safely use them as allowlisting rules. GitHub generates the remainder of each URL, the path segment and signed query string, dynamically per request, so you can't predict it.

This template was updated on December 4th, 2025 to replace the original installer and API key rotator with a new, unified deployer automation. Please disable or delete any existing installers, and create a new automation, picking the Qlik Cloud monitoring app deployer template from the App installers category.

Installing, upgrading, and managing the Qlik Cloud Monitoring Apps has just gotten a whole lot easier! With a single Qlik Automate template, you can now install and update the apps on a schedule with a set-and-forget installer using an out-of-the-box Qlik Automate template. It can also handle API key rotation required for the data connection, ensuring the data connection is always operational.

Some monitoring apps are designed for specific Qlik Cloud subscription types. Refer to the compatibility matrix within the Qlik Cloud Monitoring Apps repository.

'Qlik Cloud Monitoring Apps deployer' template overview

This automation template is a set-and-forget template for managing the Qlik Cloud Monitoring Applications, including but not limited to the App Analyzer, Entitlement Analyzer, Reload Analyzer, and Access Evaluator applications. Leverage this automation template to quickly and easily install and update these or a subset of these applications with all their dependencies. The applications themselves are community-supported; and, they are provided through Qlik's Open-Source Software (OSS) GitHub and thus are subject to Qlik's open-source guidelines and policies.

For more information, refer to the GitHub repository.

Features

• Can install/upgrade all or select apps.
• Can create or leverage existing spaces.
• Programmatically verified prerequisite settings, roles, and entitlements, notifying the user during the process if changes in configuration are required, and why.
• Installs latest versions of specified applications from Qlik’s OSS GitHub.
• Creates required API key.
• Creates required analytics data connection.
• Creates a daily reload schedule.
• Reload applications post-install.
• Tags apps appropriately to track which are installed and their respective versions.
• Supports both user and capacity-based subscriptions.

Requirements

The user running the automation needs to have:

• API permission; see Permission settings — Features and actions | help.qlik.com.
• The tenant admin role; see Permissions granted by security roles | help.qlik.com.
• The audit admin role (when deploying the Answers Analyzer application); see Permissions granted by security roles | help.qlik.com.

Configuration

Update just the configuration area to define how the automation runs, then test run, and set it on a weekly or monthly schedule as desired.

Configure the run mode of the template using 7 variable blocks

Users should review the following variables:

1. configuredMonitoringApps: contains the list of the monitoring applications which will be installed and maintained. Delete any applications not required before running (default: all apps listed).
2. refreshConnectorCredentials: determines whether the monitoring application REST connection and associated API key will be regenerated every run (default: true).
3. reloadNow: determines whether apps are reloaded immediately following updates (default: true).
4. reloadScheduleHour: determines at which hour of the day the apps reload at for the daily schedule in UTC timezone (default: 06)
5. sharedSpaceName: defines the name of the shared space used to import the apps into prior to publishing. If the space doesn't exist, it'll be created. If the space exists, the user will be added to it with the required permissions (default: Monitoring - staging).
6. managedSpaceName: defines the name of the managed space the apps are published into for consumption/ alerts/ subscription use.If the space doesn't exist, it'll be created. If the space exists, the user will be added to it with the required permissions (default: Monitoring).
7. versionsToKeep: determines how many versions of each staged app is kept in the shared space. If set to 0, apps are deleted after publishing. If a positive integer value other than 0, that many apps will be kept for each monitoring app deployed (default: 0).

App management:

If the monitoring applications have been installed manually (i.e., not through this automation), then they will not be detected as existing. The automation will install new copies side-by-side. Any subsequent executions of the automation will detect the newly installed monitoring applications and check their versions, etc. This is due to the fact that the applications are tagged with "QCMA - {appName}" and "QCMA - {version}" during the installation process through the automation. Manually installed applications will not have these tags and therefore will not be detected.

FAQ

Q: Can I re-run the installer to check if any of the monitoring applications are able to be upgraded to a later version?

A: Yes. The automation will update any managed apps that don't match the repository's manifest version.

Q: What if multiple people install monitoring applications in different spaces?

A: The template scopes the application's installation process to a managed space. It will scope the API key name to `QCMA – {spaceId}` of that managed space. This allows the template to install/update the monitoring applications across spaces and across users. If one user installs an application to “Space A” and then another user installs a different monitoring application to “Space A”, the template will see that a data connection and associated API key (in this case from another user) exists for that space already. It will install the application leveraging those pre-existing assets.

Q: What if a new monitoring application is released? Will the template provide the ability to install that application as well?

A: Yes, but an update of the template from the template picker will be required, since the applications are hard coded into the template. The automation will begin to fail with a notification an update is needed once a new version is available.

Q:I have updated my application, but I noticed that it did not preserve the history. Why is that?

A: Each upgrade may generate a new set of QVDs if the data models for the applications have changed due to bug fixes, updates, new features, etc. The history is preserved in the prior versions of the application’s QVDs, so the data is never deleted and can be loaded into the older version. 

The Upgrade of Qlik Sense Enterprise for Windows fails on the Qlik Dispatcher Service with:

ERROR: schema "MobilityRegistrarService" already exists
ERROR:  schema "qlik_notifier_service" already exists

Environment

• Qlik Sense Enterprise on Windows 

Resolution

The solution to this issue requires modifications to the database. Prior to applying the solution, take a backup. See Backup and Restore.

To resolve this, we will rename the 'qlik_mobility_registrar_service' (i.e. qlik_mobility_registrar_service_old) as well as the 'qlik_notifier_service' schema prior to performing the installation/upgrade.

This will allow for the creation of the schema. In multi-node environments, it is suggested to rename the schema prior to each rim node installation/upgrade.

To rename the schema, perform the following steps:

1.  Log on to the server running the PostgreSQL server
2. Use pgAdmin to access the database (Installing and Configuring PGAdmin 4 to access the PostgreSQL database used by Qlik Sense or NPrinting)
3. Expand the SenseServices database so that Schemas is displayed and then expand Schemas so that the qlik_mobility_registrar_service schema is displayed
4. Right-click the qlik_mobility_registrar_service and choose Properties
5. Rename the qlik_mobility_registrar_service and click Save (i.e.  qlik_mobility_registrar_service_old)
6. Repeat 4 to 5 for qlik_notifier_service.
7. Run the Qlik Sense server installer on the Rim node

Cause 

The upgrade from November 2019 to February 2020 failed on the dispatcher service with the following error on the installation log:

CAQuietExec:  MobilityRegistrarService configuration started.
CAQuietExec:  WARNING: Skiping the database initialization. No superuser or password 
CAQuietExec:  specified.
CAQuietExec:  Creating schema 'qlik_mobility_registrar_service'.
CAQuietExec:  True
CAQuietExec:  Error executing database command "CREATE SCHEMA 
CAQuietExec:  "qlik_mobility_registrar_service" AUTHORIZATION "qliksenserepository"": ERROR: 
CAQuietExec:   schema "qlik_mobility_registrar_service" already exists
CAQuietExec:  At C:\Program Files\Qlik\Sense\MobilityRegistrarService\install\install-utils\P 
CAQuietExec:  ostgres.ps1:113 char:11
CAQuietExec:  +           throw  "Error executing database command  ...
CAQuietExec:  +           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CAQuietExec:      + CategoryInfo          : OperationStopped: (:) , Exception
CAQuietExec:      + FullyQualifiedErrorId : Error executing database command "CREATE SCHEMA  
CAQuietExec:     "qlik_mobility_registrar_service" AUTHORIZATION "qliksenserepository"": ER  
CAQuietExec:    ROR:  schema "qlik_mobility_registrar_service" already exists
CAQuietExec:   
CAQuietExec:  Error 0x80070001: Command line returned an error.
CAQuietExec:  Error 0x80070001: QuietExec Failed
CAQuietExec:  Error 0x80070001: Failed in ExecCommon method
CustomAction CA_SetupQMR returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

When SMTP is used to send outgoing mail and the legacy DigiCert G1 SSL cert provided by Microsoft to Qlik is still in use, emails sent from Qlik Cloud will fail. 
 

Resolution

The SMTP endpoint must present a chain anchored to a currently trusted DigiCert root (for example: Global Root G2, with the correct intermediate), supported by DigiCert and already used by modern Microsoft/O365 endpoints.
 

Cause

Qlik Cloud does not support the legacy DigiCert Global Root CA (G1), which was dropped from the SMTP bundle due to security concerns (see Review the G1 root removal advisory | docs.digicert.com).

This blocks the use of a locally issued certificate when the endpoint relies on G1.

Internal Investigation ID(s)

SUPPORT-10911

Environment

• Qlik Cloud

The Qlik Sense on Windows Content Monitor is intended for Qlik Administrators. Its purpose is to monitor and analyze your Qlik Sense content, including app usage, resource consumption, and data sources. This helps with governance, optimization, and identifying unused content.

Requirements

• Platform: Qlik Sense Enterprise on Windows
• Version: November 2025 onwards 
• Availability: Bundled with installation from version November 2025 onwards
• If you are running previous versions of Qlik Sense Enterprise on Windows, the Content Monitor is also available on Qlik's Downloads page here: Content Monitor (download page)
  • This must be manually installed, and a weekly reload is recommended.
  • The downloaded version is supported from Qlik Sense version Feb 2020.

Core Documentation

All technical details can be found in the two attached documents. These are your primary resources.

Qlik Sense Content Monitor User Guide

• • What it covers: A detailed, sheet-by-sheet explanation of the entire app. It describes what every KPI, chart, and table means for sections like "Weekly Summary," "Snapshot," "Applications," "Sessions," "Task Executions," "File Inventory," and "Infrastructure."

  • Use Case: 

    • Guiding a customer on how to read and interpret the data.

    • Answering customer questions like, "What does the 'Session Concurrency' sheet show?" or "How do I read the 'File Inventory' sheet?"

  • See the attached Qlik Sense Content Monitor User Guide

Configuration Guide

• • What it covers: This is the primary guide for setup and reload issues. It contains:

    • Detailed definitions for all script parameters (e.g., vCentralNodeHostName, vVirtualProxyPrefix, vServerLogFolder).

    • Performance tuning options (e.g., vFileScanMaxDuration, vAppRetrievalLoop, exclusion lists).

    • A "Trial Mode" section is used for troubleshooting initial reload failures.

    • A "Troubleshooting" section.

  • Use Case:

    • New installations.

    • Troubleshootings.

    • Tuning performance for long reloads.

  • See the attached Qlik Sense Content Monitor Configuration Guide

Environment

• Qlik Sense Enterprise on Windows

Loading data from the source (PostgreSQL/Raw) to the Teradata target via JDBC using the tDBOutput component in Talend Studio may lead to the following write error:

[ERROR] tDBOutput - [Teradata Database] [TeraJDBC 20.00.00.58] [Error 6706] [SQLState HY000] The string contains an untranslatable character.

Environment

• Talend Studio

Resolution

• DDL Update: Update the non-Unicode table column definitions on the Teradata target to unified Unicode-based types (e.g., NVARCHAR / CHARACTER SET UNICODE).
• JDBC Configuration: Apply CHARSET=UTF8 to the JDBC connection string to align session parameters with incoming data streams.

After applying the changes, verify the write operations. Data loading will resume successfully without untranslatable character errors.

Cause

The issue was identified as a character-set conversion failure. Analysis of the Teradata table DDL revealed that certain target columns were configured with non-Unicode definitions (e.g., standard VARCHAR without Unicode encoding), preventing Teradata from storing multi-byte character strings passed from Talend during insertion.

Environment

• Talend Studio

Some versions of Qlik Sense Desktop show a significant delay when opening the hub after authenticating through Qlik Cloud.

Affected versions

• Qlik Sense Desktop November 2025 SR 1
• Qlik Sense Desktop May 2026 IR

Resolution

A fix to QCB-35278 is expected in August 2026. 

Information provided on this defect is given as is at the time of documenting. For up-to-date information, please review the most recent Release Notes for updates on ID QCB-35278.

Cause

Defect QCB-35278 is caused by the Qlik Cloud backend introducing a delay during the login process.

Internal Investigation ID(s)

QCB-35278, SUPPORT-10476

Do Qlik Products support the use of Standalone Managed Service Accounts (GMSA)?

At this time, QlikView, Qlik Sense Enterprise on Windows, and Qlik NPrinting do not support the use of managed service accounts.

For general service account requirements, see:

QlikView Service Account Requirements 
Qlik Sense Enterprise on Windows Service Account Requirements 
Qlik NPrinting user account requirements 

Environment

Qlik Sense Enterprise on Windows 
Qlik NPrinting 
QlikView 

When using Cidaas as an OIDC Identity Provider in Qlik Cloud, the first login works successfully. After logging out and attempting to log in again in the same browser session, authentication fails with the following error:

STATE-1 – State verification failed
State parameter not valid, try accessing the tenant url directly

The issue does not occur if the browser is completely closed and reopened before the second login attempt.

Resolution

To resolve the post-logout STATE-1 error with Cidaas, improve logout session cleanup by configuring proper Post-Logout Redirect and End Session handling on both sides.

1. In the Qlik Cloud Administration center, go to  Identity Providers and edit your Cidaas OIDC configuration.
2. Set the Post logout redirect URI to your tenant root URL (e.g. https://your-tenant.de.qlikcloud.com/).
3. Configure the End session endpoint with the value provided by Cidaas (typically something like https://your-cidaas-domain/oauth2/endsession).
4. In your Cidaas tenant configuration:
   • Add the Qlik tenant URL(s) to the allowed Post-logout redirect URIs.
   • Ensure the client/application supports OIDC RP-Initiated Logout.
5. Save changes and test the full flow: Login > Logout (via Qlik UI) > reopen the tenant URL in the same browser.
6. As a temporary workaround, advise users to fully close the browser after logging out or use Incognito mode.

Always test logout flows thoroughly with custom IdPs like Cidaas. Use exact URLs (no trailing slash mismatches) for Redirect URI and Post-logout redirect URI.

Cause

This issue is specific to the interaction between Qlik Cloud’s strict OIDC state validation and Cidaas logout behavior. Qlik Cloud uses a short-lived browser cookie (eas.rfp.<random>) tied to the OAuth2/OIDC "state" parameter for CSRF protection.

During the first login, everything works. However, when the user logs out of Qlik, the session cookies (including eas.rfp) are not fully cleared or invalidated on the browser side. On the subsequent login attempt in the same browser:

• Cidaas redirects back with a new state parameter.
• Qlik’s edge-auth service still sees stale session context from the previous login.
• This causes a mismatch ("State not valid" + often "Session not found" or "tenantId does not match").

Fully closing the browser clears the residual cookies, which is why a fresh browser session works. This is a common pattern when Post-logout redirect and End Session endpoints are not properly configured for clean session termination.

Related Content

• Qlik Sense SaaS: Authentication fails when using cidaas as an Identity Provider (Groups issue)

Environment:

• Qlik Cloud
• Cidaas as custom OIDC Identity Provider

The information in this article is provided as-is and will be used at your discretion. Depending on the tool(s) used, customization(s), and/or other factors, ongoing support on the solution below may not be provided by Qlik Support.

The same expression with aggregation functions and an Inter-record function can yield different results depending on the situation, especially when data is loaded from different QVDs.

Affected Inter-record functions can be Above(), Below(), Bottom(), Top(), NoOfRows().

The results shown in the app when it is loaded on-premises may differ from those when the app is loaded on Qlik Cloud.

An example of an expression that can be affected by the problem is:

Aggr(RangeSum(Above(Sum(CHK_ORDER_ID), 0, RowNo())), CUSTOMER_ID), '')

Resolution

To avoid this problem, add a structured sort parameter directly inside the Aggregation function, forcing a consistent evaluation order regardless of how the underlying data arrived.

For example, the formula above should be:

Aggr(RangeSum(Above(Sum(CHK_ORDER_ID), 0, RowNo())), (CUSTOMER_ID, (Numeric, Ascending)))

Because Above() is used, sorting on other columns in the same straight table is disabled by design in Qlik Cloud. The same is valid for other functions, like Below().

The Aggr() sort parameter controls the order used for the running total calculation itself, but you will need to keep that sort definition aligned with the order you actually want the counter to reflect. If CUSTOMER_ID is a date or text field rather than numeric, replace (Numeric, Ascending) with (Text, Ascending) or (Date, Ascending) accordingly.

Cause

Inter-record functions depend entirely on the physical row order of the data as the engine sees it, and that order can change for different reasons, producing inconsistent results. For example, on-premises and Qlik Cloud can handle the internal sort of concatenated data differently, which explains why the counter is not the same in the two environments.

A reference to the problem can be found in the Community post Solved: Above Function in qlik sense.

Environment

• Qlik Cloud Analytics
• Qlik Sense Enterprise on Windows

Qlik Data Gateway is shown as disconnected. Reviewing the Qlik Data Gateway logs shows:

System.Net.WebSockets.WebSocketException (0x80004005): The server returned status code '401' when status code '101' was expected.

Resolution

The error indicates Qlik Data Gateway may not be installed on a dedicated machine, that the time shared between hosts may be incorrect, or that the setup was not completed correctly.

Do not install Qlik Data Gateway on the actual server or on a server that hosts Qlik Sense Enterprise on Windows or, for example, Qlik Data Transfer.

Local Time on one host

Verify that both hosts use the same time zone and their times are aligned.

If the Windows server time is unaligned (due to, for example, an internal battery issues), the Direct Access Gateway will disconnect.

Incorrect setup

In rare cases, Qlik Data Gateway may not have been set up correctly. In this case, follow the below instructions on how to perform a clean re-install:

1. Uninstall Qlik Data Gateway.
   
   
2. Restart your server.
   
   
3. Reinstall Qlik Data Gateway but do not start the Qlik Data Gateway service and do not change the service account.
   
   
4. Run this below command in an elevated command prompt and from C:\Program Files\Qlik\ConnectorAgent\ConnectorAgent
   
   connectoragent qcs set_config --tenant_url XXXX.YYYY.qlikcloud.com
   
   Where XXXX= is your Tenant Name and YYYY= is your Tenant Region.
   
   
5. Run:
   
   connectoragent qcs generate_keys
   
   
6. Run:
   
   connectoragent qcs get_registration
   
   
7. Copy the key and go to your Tenant's Management Console and data-gateway URL (example: https://YOURTENANTNAME.YOURREGION.qlikcloud.com/console/data-gateway/)
   
   
8. And create your deployment as described in Installing Qlik Data Gateway - Direct Access
   
   
9. After all the above is finished, start the Qlik Data Gateway service.

Related Content 

System requirements | Qlik Cloud Help 

Environment

Qlik Data Gateway  

The Qlik Reporting Add-in may display the following error when connecting to a Qlik Cloud tenant from Microsoft Word, Excel, or PowerPoint:

The security settings in your browser prevent us from creating a dialog box. Try a different browser, or configure your browser so that [Qlik Cloud Tenant] and the domain shown in your address bar are in the same security zone.

The problem is specifically seen with Microsoft Edge.

Resolution

To resolve this issue:

• Switch to a different browser, such as Firefox
• Or configure Microsoft Edge to allow the pop-up:
  1. In Microsoft Edge, open Settings
  2. Type Pop-ups and redirects in the settings search bar
  3. Deselect Blocked as the Default behavior or add the Qlik Cloud tenant URL in the Allowed to send pop-ups and use redirects section. 
     
     Speak to your IT administrator for assistance if necessary.
     
     

Cause

The Microsoft add-in is a pop-up utility that requires permission from the MS Edge browser to open. 

Environment

• Qlik Cloud Reporting Add-in

The following error may trigger when executing a job in Qlik Talend Studio through a target execution:

Execution failed :org.talend.remote.jobserver.commons.utils.io.JobLimitException: Unzipped file name exceeds the maximum length: '240' (configured in org.talend.remote.jobserver.commons.config.JobServerConfiguration.MAX_UNZIPPED_FILE_NAME_LENGTH) [Unzipped file name exceeds the maximum length: '240' (configured in org.talend.remote.jobserver.commons.config.JobServerConfiguration.MAX_UNZIPPED_FILE_NAME_LENGTH)]

Resolution

To resolve, set the MAX_UNZIPPED_FILE_NAME_LENGTH=1024 parameter in both the Remote Engine org.talend.remote.jobserver.server.cfg and Talend Studio.ini file:

• Remote Engine/etc/org.talend.remote.jobserver.server.cfg:
  

   org.talend.remote.jobserver.commons.config.JobServerConfiguration.MAX_UNZIPPED_FILE_NAME_LENGTH=1024

• Studio.ini:
  

  Dorg.talend.remote.jobserver.commons.config.JobServerConfiguration.MAX_UNZIPPED_FILE_NAME_LENGTH=1024

Environment

• Talend Studio

A reload task in QlikView fails with the following error in the task log:

Error The sourcedocument failed to save.. Exception=System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component. || at QlikView.Doc.SaveAs(String _FileName, Int16 _Format) || at QVBWrapper.Document.Save(ILogBucket i_LogBucket, String i_SaveAsFileName)

This may be caused by an active virus scan locking the relevant files, or an invalid alert configured on the task.

• QlikView

Virus Scan

Ensure that QlikView file locations (.qvw, qvd, etc..) are excluded from active virus scans. See QlikView Folder And Files To Exclude From Anti-Virus Scanning .

Invalid Alerts

Remove or edit the alerts configured on the document.

Alerts can be configured in the Distribution task. To verify:

• Open the QlikView Management Console
• Go to Documents > Source Documents
• Locate the failing document/task.
• Open the document/task
• Navigate to the Distribute tab
• Go to the Notify tab.
• Uncheck Send notification e-mail to recipients 
• Make sure, there is enough disk space to save the QVW

For additional troubleshooting steps and root causes, see QlikView: Checklist For Reload/Publisher Task Failure.

Your AI is only as good as what it can find. 

Part One of How to prepare your Qlik App for Qlik Answers laid out a six-step checklist:

• clarify field names,
• streamline the data model,
• check date formats,
• build master items with descriptions,
• configure vocabulary,
• and validate with real queries.

It ended with a simple line: you do not need a perfect data model, you need a clear one. This is what clear means underneath the surface. Keep the shortlist clean, and the model's fluency has good material to work with.

Part Two details what Qlik Answers is doing when it reads your apps and expands your understanding of why those six steps move the needle.

Content

• The mental model: retrieval rather than omniscience
• Lever 1: Visibility
• Lever 2: Names
• Lever 3: Master items
• Lever 4: Descriptions
• Lever 5: Vocabulary
• In Summary

The mental model: retrieval rather than omniscience

It is easy to assume the AI "sees" your entire app and simply needs to be clever enough to choose well. In practice it works a little differently, and for good reason. An app with 500 fields would present far more noise than signal to any model.

Instead, the system builds a search index of your app's metadata. Every visible field and master item gets a compact semantic profile, and that profile is what the system searches against.

For a master measure, that profile is built from several signals together:

• the name of the master item
• the description you have written for it
• the actual expression behind it
• any business glossary term you have linked to it

The system reads these as a whole and forms one understanding of what the asset means. When a question arrives, it retrieves the handful of assets that best match its meaning and passes them to the AI.

That single idea reframes the work. The useful question is rarely "is the AI clever enough to understand my field?" More often it is "will my field be found, and will it be the natural choice when it is?"

We'll tackle this in order, using five different levers. These levers act at different stages, which is why the sequence in which we outline them is important. Visibility decides what exists. Names influence what gets found first. Master items shape what the AI builds your numbers with and whether they carry your definitions. Descriptions help the right things get found at all. Vocabulary closes the last gap between your words and the model's understanding.

Working the later levers on an app still full of visible technical fields means refining assets that are competing with a great deal of noise. It tends to go more smoothly to start with the gate, then the definitions, then the language.

Lever 1: Visibility

The one truly decisive setting.

Hiding a field in your business logic does more than lower its priority. It takes the field entirely out of consideration. A hidden field is never profiled, never indexed, and never retrievable, so it cannot appear in an answer.

That is why visibility is worth looking at first. Every technical field left visible, every surrogate key, ETL timestamp, or FIELD_CODE_2_FINAL, competes with your real business fields. Working through a wide app and hiding the fields that should never be an answer is usually a few hours of work, sometimes less, and it improves every question asked afterwards. It is one of the most approachable, high-value things you can do to an app.

Hide with intent. If people do ask about a field, hiding it takes away their ability to get answers about it. Think of this as curation rather than cleanup.

Lever 2: Names

Names carry weight in retrieval.

When a question contains a term that closely matches an asset's name, that asset is favored strongly in the results.

So it pays to name assets the way your users actually speak. If everyone in the business says "Net Revenue", a master measure called "Net Revenue" tends to be found quickly and reliably. One called "NR_calc_v3" leaves the system to infer what you meant. It often will, and it is worth giving it a clear signal where you can do so easily.

Lever 3: Master items

Define your metrics once, with care.

Master items sit high on this list for a straightforward reason: when a well-defined master item and a raw field could both answer a question, the system leans toward the master item. It is your sanctioned, promoted answer.

The stronger argument, though, is trust rather than mechanics. The model does understand what "net sales" means in general terms. The question is whether you would prefer it to work from the general idea or from your definition.

Does your net sales exclude intercompany transfers? Is it net of returns or gross of them? Which currency, at which exchange rate, over which fiscal calendar? Answered from raw fields, each of those becomes a reasonable assumption. Answered through a master measure, it follows your business logic, your set analysis, and your exceptions, consistently. When the number reaches a report your leadership is reading, a defined metric gives everyone confidence in where it came from. Define the metric once, as a master item, and every answer built on it inherits the definition you stand behind.

It is worth building a master item for every metric that carries a real business definition, while keeping the library tidy. A collection of "Sales", "Sales 2", and "Sales New" tends to reintroduce the very ambiguity master items are meant to resolve, so clear naming here matters as much as the definitions themselves.

Lever 4: Descriptions

Think of them as configuration rather than documentation.

Descriptions are often treated as a nice-to-have for the data catalog. In an AI-ready app, they do more.

The description you write on a field or master item feeds directly into its semantic profile, which is what the system searches. A clear note on what "Net Sales" includes and excludes helps that item surface for the many ways people might phrase the question, and sets it apart from the other sales measures nearby.

There is no need to describe everything. The ones worth your time are the ambiguous ones: lookalike measures, fields whose names are abbreviations, anything a new analyst would have to ask a colleague about. If a person would want the explanation, the search index benefits from it too.

Lever 5: Vocabulary

Focus on your language, not on educating the model.

This is the lever people tend to overthink, so it is worth being clear about its purpose. You are not here to teach the AI general knowledge. There is a genuinely capable model underneath, and it already understands a great deal of the world.

It knows what revenue, profit, and margin are. It understands churn, retention, and attrition. It is comfortable with YoY, MoM, and QoQ, with fiscal quarters, gross versus net, currencies, countries and regions, standard units, and the everyday language of sales, finance, and operations. There is little value in a glossary entry explaining that "revenue" means money coming in.

Where vocabulary earns its keep is the language that is specific to you, which the model has no way to know:

• Your internal product codenames.
• An acronym only your company uses.
• The name your business gave to a segment it defined itself.
• A regional grouping that exists only on your org chart.
• If your business says "GMV" and the field is named "Gross_Merch_Value"

Those are examples the model cannot bridge on its own, and this is precisely where a vocabulary entry helps.

So a small, proprietary vocabulary tends to serve you best. A handful of terms that are truly yours will often do more than a long list restating things the model already knew. Vocabulary is a useful tool with a focused job: teaching the model your dialect rather than the dictionary.

Two items from that checklist do not appear as levers above: date formats and validation. Neither is a retrieval signal. A Date or Timestamp tag is a data type requirement your time-based questions depend on, not something the search index weighs when it ranks assets. Validating with real queries is not a lever at all. It is how you find out whether the five above actually worked.

In Summary

When people ask your app questions in plain language, the AI does not read your whole data model. It searches a curated index of your fields and master items, retrieves a small shortlist, and reasons over that. Most of what helps an app answer well comes down to making sure the right assets land on that shortlist. A sensible order to work through: hide what should never be an answer, name assets the way your users talk, define your real metrics as master items, describe the ambiguous ones, and add vocabulary for the terms that are genuinely yours.

Environment

• Qlik Cloud
• Qlik Answers

The Model Context Protocol (MCP) is an open standard that lets AI assistants connect to external data sources and tools.

This article provides step-by-step instructions for connecting Mistral Vibe to the Qlik MCP server in any tenant. Once connected, you can ask Mistral to check something in Qlik for you, live, instead of you tabbing over to do it yourself.

Content

• Before you start
• What you'll need
• Mistral Vibe web app (chat.mistral.ai)
• Vibe CLI
• Troubleshooting

Before you start

Mistral gives you two separate places to do this, and they don't share their setup: the Mistral Vibe web app (formerly known as "Le Chat":chat.mistral.ai) and the Vibe CLI (the terminal tool). Pick the article section for the one you actually use. If you use both, you'll need to do both; no shortcut covers the two at once.

What you'll need

• An account with a Qlik Cloud Tentant Admin role, with the appropriate user permission for MCP (see Qlik MCP server access and permissions | help.qlik.com).
• The MCP Qlik Cloud tenant URL: https://<name>.<region>.qlikcloud.com/api/ai/mcp

  Recommendation: Copy the URL; a typo leads to a silent failure during setup.

Mistral Vibe web app (chat.mistral.ai)

This path creates what Mistral calls a Connector: a connection to the Qlik MCP server that Mistral hosts and manages for you, usable from chat.mistral.ai (and Work, if your org has it). It's registered once on console.mistral.ai, Mistral's Studio, and from then on it just shows up as something you connect to like any other integration.

Step 1: Add a Connector in Studio

1. Log into console.mistral.ai
2. Go to Build > Connectors (or head straight to console.mistral.ai/build/connectors). 
3. Click + Add Connectors on the top right corner
   
   
   
   

Step 2: Create the connector and authenticate

1. Go to Custom MCP Connector 
2. Fill out the form:
   • Name: Connector name in Mistral (this is the name you will reference later)
   • Description: Connector Description
   • Server URL: https://<name>.<region>.qlikcloud.com/api/ai/mcp
   • Visibility: private if the connection is only intended for you, shared_workspace if your whole team should get it
     
     
     
     
3. Continue by filling out Authentication information, keeping the Authentication Method to Auto-detect. Mistral will select OAuth 2.1.

   Mistral OAuth requires Dynamic Client Registration; see Configuring OAuth dynamic client registration | help.qlik.com.

4. Leave the OAuth 2.1 Advanced settings (Redirect URI, Client ID, Client Secret) as they are
5. Click Create
   
   
   
   
6. You are redirected to the login page as defined in Qlik Cloud (your identity provider or Qlik Account if there is no identity provider specified in the tenant).
7. Click Approve 

   You must be logged in as a Tenant Admin.

   

Step 4: Use the connection in chat.mistral.ai

1. Open chat.mistral.ai
2. Go to Connectors in the + icon at the bottom left of the chat bubble, and select Qlik MCP Server (the actual name of your MCP connector in Mistral Studio).
   
   
   
   Qlik MCP Server will show up in the bubble chat, ready to use (in our example, the connectors are both MCP presales-iberia and Qlik MCP Server; in your case, it will show the name previously provided).
   
   From here, ask Mistral something that needs Qlik, and it'll reach for it on its own.

Vibe CLI

The Vibe CLI doesn't read Studio Connectors, at least not yet, so even if you already set up a Studio Connector, you will still need to complete the CLI setup separately to define the MCP server inside Vibe. 

To obtain and install Vibe CLI, follow the steps in Install the Vibe CLI and send your first prompt | docs.mistral.ai.

Step 1: Add the Qlik Server

1. Open Vibe from the terminal with the command:

   vibe

2. Once you see Vibe's prompt, add the Qlik server with the following command, including your tenant name and region, as well as the name you want to give your MCP Server.
   
   In our example, we use qlik_mcp_server_cli as the name; yours can be any descriptive text that helps you identify the Qlik MCP Server connection in the Vibe CLI.
   

   /mcp add https://<name>.<region>.qlikcloud.com/api/ai/mcp --name qlik_mcp_server_cli --scope user_default --scope mcp:execute --transport streamable-http

   
   
   
   
3. You will see a line confirming the server was added, then "Starting OAuth login...".

   At the time of writing, Vibe will experience a defect at this exact step. It cannot finish logging in on the first try, failing with the error:
   
   Error: No MCP servers configured.
   
   
   
   This is a known defect in Vibe CLI 0.21.0. Track it at bug: /mcp add on the first-ever MCP server fails to log in with "No MCP servers configured."

Step 2: Exit and reopen Vibe

1. Exit Vibe using the command:

   /exit

2. Open Vibe with the command:

   vibe

Step 3: Complete signing in to Qlik

1. Begin the login process with the following command, replacing qlik_mcp_server_cli with the name you set previously.

   /mcp login qlik_mcp_server_cli

   Vibe prints a web address and tries to open your browser for you. If nothing opens, copy that URL and paste it in a browser window yourself.
   
   
   
   
2. Log in with your Qlik Cloud tenant admin and click Approve. 
   
   
   
   Once completed, close that tab and return to the terminal.
   
   
3. Confirm the setup was successful by running the command:

   /mcp status

4. Look for your Qlik MCP server name in the list and verify it is listed as authenticated, not as needs auth.
   
   It will show 60 tools at the time of this writing; as Qlik continuously evolves the MCP server, this number may vary in the future.
   
   
   
   Qlik MCP Server is now live in Vibe.
   
   

Where the configuration is saved

All of this writes to one file: ~/.vibe/config.toml (by default /Users/<you>/.vibe/config.toml on a Mac and C:\Users\<you>\.vibe\config.toml). You don't need to touch it by hand, /mcp add does it for you, but it helps to know what "it worked" looks like on disk.

You will be able to find the following near the bottom of the file:

[[mcp_servers]]
name = "MCP Server Name"
transport = "streamable-http"
url = "https://<tenant>.<region>.qlikcloud.com/api/ai/mcp"

[mcp_servers.auth]
type = "oauth"
scopes = [
    "user_default",
    "mcp:execute",
]

If you ever want to double-check the setup, or remove it and start over, this is the block you're looking for.

Troubleshooting

"Error: No MCP servers configured." right after /mcp add (Vibe CLI). The known bug in Mistral Vibe. Exit Vibe, reopen it, run /mcp login MCP-Server-Name again. This will be resolved once Mistral ships the fix.

502 error when trying to log in (Vibe CLI). This means the CLI has been pointed at the Studio Connector instead of a server defined inside Vibe itself, usually by reusing its OAuth URL or trying to log in through it directly. It won't work, and it can't: the CLI doesn't know how to talk to a Studio Connector. The fix isn't a retry; it's going back to the setup and completing the Vibe CLI connection.

Browser doesn't open on its own during login (either Studio or Vibe CLI). Copy the URL that was printed and paste it in yourself.

/mcp status still says "needs auth" after you logged in (Vibe CLI). Make sure the browser actually showed you a success screen before you closed it. If it did and the status still looks wrong, just run /mcp login MCP-Server-Name again.

Not sure which section you need? If you're chatting with Mistral in a browser, use Studio. If you're typing into the Vibe CLI in a terminal, use the Vibe CLI section. Doing one doesn't undo or interfere with the other.

Environment

• Qlik MCP
• Qlik Cloud

The Microsoft Fabric Connector is not currently supported as a target system.

A connection using the Azure Storage connector may succeed and pass testing, but reloads will fail with "Operation not supported" on the specific endpoint.

Qlik is actively working on enhancements to provide the functionality in the future: 

• TLV-2349: New Connector for Microsoft Fabric (Discovery)
• TLV-1841: Qlik Open Lakehouse (Iceberg) Connector for Qlik Analytics (Discovery)

A specific release date has not yet been determined.

Stay up to date with the Qlik Cloud changelog. 

Environment

• Qlik Cloud Analytics

After an upgrade to QlikView September 2025 SR1, tasks defined in the QlikView Management Console using an external program fail.

The QlikView server's Windows Event log shows the following error:

Faulting application name: Qv.exe, version: 12.100.20100.0, time stamp: 0x692464ea
Faulting module name: ntdll.dll, version: 10.0.20348.4893, time stamp: 0xfd32fdb3
Exception code: 0xc0000005

Affected versions:

• QlikView September 2025 SR 1

Resolution

This is a known QV.exe defect (QCB-34453). Upgrade to QlikView September 2025 SR 2 or later releases.

Information provided on this defect is given as is at the time of documenting. For up-to-date information, please review the most recent Release Notes or contact support with the ID QCB-34453 for reference.

Cause

Product Defect ID: QCB-34453

Amazon S3 V2 connections and reloads fail with the following error:

Could not load file or assembly 'System.Text.Json, Version=6.0.0.11, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) 

Affected versions:

• Qlik Sense Enterprise on Windows November 2024 SR 25 and SR 26
• Qlik Sense Enterprise on Windows May 2025 SR 15 to SR 18
• Qlik Sense Enterprise on Windows November 2025 SR 3 to SR 8

Resolution

This is a known defect (SUPPORT-8609). QvWebStorageProviderConnectorPackage.exe.config is not correctly overwritten during the upgrade process.

Upgrade to the following versions:

• Qlik Sense Enterprise on Windows November 2024 SR 27 or higher
• Qlik Sense Enterprise on Windows May 2025 SR 19 or higher
• Qlik Sense Enterprise on Windows November 2025 SR 9 or higher

Information provided on this defect is given as is at the time of documenting. For up-to-date information, please review the most recent Release Notes or contact support with the ID SUPPORT-8609 for reference.

Cause

Product Defect ID: SUPPORT-8609