Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Mar 26, 2026 9:12:07 AM
Mar 17, 2026 10:35:59 AM
This article answers the most frequently asked questions about Qlik Discovery Agent. It is split into five sub-sections:
If you are looking for information on how to get started, check out the Discovery Agent Interactive Walkthrough and our Discovery Agent Documentation.
Discovery Agent is an AI-powered, always-on monitoring capability in Qlik Cloud that automatically detects meaningful changes, anomalies, and trends in your data. It requires no rules, thresholds, or manual setup. Discovery Agent identifies spikes, drops, trend shifts, baseline changes, and data quality issues, then delivers clear, plain-language insights in a prioritized feed.
Traditional BI alerts rely on predefined thresholds or manual logic. Discovery Agent uses the Qlik Analytics Engine and its associative capabilities to evaluate wide combinations of data relationships automatically and proactively surface only those insights that matter. It is context aware, adaptive, and far more scalable than rules driven systems.
Yes. Discovery Agent is built directly into Qlik Cloud Analytics and leverages the Qlik Analytics Engine for associative, large scale anomaly detection.
Yes. You can ask questions directly from an insight card, and context from the insight will be transferred into Qlik Answers.
No. Discovery Agent is built exclusively for Qlik Cloud.
No. Monitoring runs outside active dashboards, ensuring no performance impact on live analytics experiences.
Yes. Insight delivery respects user permissions, governed access, and security boundaries.
Discovery Agent analyzes updated app data models using associative evaluation to identify:
No rules or thresholds are required.
Discovery Agent is always on, but processes changes when the application’s data model updates. Insights refresh after reload and appear in the feed once the system evaluates new data. Updated are currently capped at one reload per day.
The feed automatically refreshes upon reload. For most apps, this occurs once per day or whenever new data is introduced.
Yes. You can follow specific apps or insight categories once the Following tab is released. Filtering options are also planned to help tailor results.
Insight Triggers are structured metric definitions that serve as the foundation for generating analytical insights within the application. Each trigger is composed of a measure or expression, such as a calculated field or KPI, along with a set of additional configuration parameters. These parameters include the frequency at which the trigger evaluates data and the type of calculation to be applied (example: sum, average, count).
Together, these elements define the conditions under which an insight is surfaced to the user.
Yes, a date period is required for every trigger you configure.
All insights generated by the system are trend-based, meaning they analyze data over time to identify patterns, changes, or anomalies. This requires a date period to be added to the trigger's associated group. Without a defined time range, the system cannot perform the temporal comparisons necessary to produce meaningful insights.
The Insight Feed refreshes automatically each time the page is reloaded. No manual refresh action is required. The feed itself is regenerated once per day, and this regeneration is triggered by the introduction of new data into the application or applications that contain active triggers. As a result, the feed will always reflect the most recent data available as of the last daily reload cycle.
Filtering functionality is available in the Feed. A Filter button is currently visible at the top of the feed during the preview phase of the application. Users can use this to find specific insights in the feed.
Triggers are stored directly within the application in which they are created. They are not stored externally or in a centralized repository. That means each application manages its own set of triggers independently, and triggers defined in one application will not carry over to or affect another application.
Direct question-and-answer functionality within the feed is available.
The Insight Feed is integrated with Qlik Answers, enabling users to ask natural language questions without leaving the feed interface. Because each card displayed in the feed is tied to a specific application, context from the relevant card will be automatically transferred to Qlik Answers to ensure accurate, contextually appropriate responses.
This behavior is expected and occurs specifically after the first reload following the creation of new triggers.
During this initial reload, the system performs a comprehensive scan of all available historical data, rather than only the most recent data. This allows it to identify any and all qualifying insights across the full dataset. This is a one-time process. All subsequent reloads after this initial one will only evaluate and surface insights based on newly introduced data, so the volume of older insights will not continue to grow with each reload.
Yes. The Insight Feed and its associated trigger functionality require the cross-region inference toggle to be enabled. Please ensure this setting is activated in your environment before attempting to configure triggers or access the feed. If you are unsure how to enable the cross-region inference toggle, contact your system administrator or refer to the relevant configuration documentation.
To remove specific insights from the Insight Feed, you must delete the trigger that is generating those insights. Because the feed is dynamically generated based on active triggers, removing a trigger will prevent its associated insights from appearing in future feed reloads.
Deleting a trigger is a permanent action.
If you wish to stop surfacing certain insights temporarily, consider whether disabling or modifying the trigger may be a more appropriate course of action, depending on your platform's available options.
Section Access is not currently supported for applications used with the Insight Feed.
Any application that has Section Access enabled is incompatible with this feature at this time. As a result, all users who have been granted access to a given application will be able to see the insights generated from that application's triggers, regardless of any Section Access restrictions that may otherwise apply within that application.
This is an important consideration when deciding which applications to configure with triggers, particularly for datasets that contain sensitive or role-restricted data. Support for Section Access may be introduced in a future release.
Below is the minimum data requirement:
Weekly/Monthly/Quarterly/Yearly aggregation
Daily aggregation
Missing dates in the date field may prevent calculations. Creating a master calendar in the
load script can resolve this. Qlik is exploring options for date imputation.