Qlik Sense Problems & Issues
Real user-reported problems, complaints, and limitations for Qlik Sense. Based on analysis of 13 signals.
Overall score: 60/100
Issues by Category
Qlik Sense learning curve is steep after the easy intro
Reviewers on G2, TrustRadius and PeerSpot say basic dashboards are quick to build but real data modeling and load scripting take much longer to learn. Non-IT users often depend on a developer.
Synthetic keys and circular references break data models
Loading tables that share more than one field creates synthetic keys, and loops create circular references. Qlik warns about both and users must remodel with composite keys or renamed fields.
Excel and file exports fail or come out truncated
Community threads describe exports that download nothing, return access denied on Desktop, or contain only part of a table.
Qlik Sense is expensive compared with Power BI and Tableau
Multiple reviewers call it pricier than average BI tools and say licensing makes wider adoption hard for small companies. Capacity-based Cloud plans start at hundreds of dollars a month billed annually.
Capacity-based pricing means paying per 25 GB of data
Standard starts at 25 GB with extra capacity sold in 25 GB increments, and overages are charged only above the plan capacity. Large datasets raise the bill fast.
Scheduled reloads fail with connection or credential errors
Reload failures from unreachable databases, expired credentials, timeouts and path problems are among the most common Qlik Community threads. The fix usually starts with the script log.
'Connection lost' error while a sheet loads
Users report sheets that load for a few seconds and then drop with Connection lost. A thread links it to memory or calculation pressure from specific table columns, though the root cause is not always confirmed.
Apps get slow with heavy expressions and weak data models
Community answers repeatedly trace slow charts to IF() and AGGR() expressions, synthetic keys and wide tables, and advise fixing the data model instead of the chart.
Out of calculation memory and calculation timed out errors
Large calculations hit the engine's hypercube memory and time limits. Qlik's own article recommends at least 16 cores and 64 GB of memory for the engine servers.
Legacy connectors and TLS versions are being retired
Qlik is ending TLS 1.1 support in May 2026 and, per its notices, ODBC connections negotiating only TLS 1.0/1.1 fail from the November 2026 client-managed release. The Web Connector is also being removed.
Extensions and add-ons needed to get the visuals you want
Review aggregators note users complaining they must pay for and install extensions to make Qlik Sense meet their needs.
Support is strong for common issues but thin for niche ones
A PeerSpot reviewer praises support for stability problems but another says niche requirements get little help. A TrustRadius reviewer says broken reports waited on a team without capacity.
Market momentum has shifted toward Power BI
SaaSWorthy-listed reviewers note adoption moving to Power BI, and a TrustRadius reviewer said they would not choose Qlik again unless an enterprise mandate required it.
Regret Patterns
Common reasons users regret choosing Qlik Sense.
Buying for the dashboards, then needing a developer
Teams discover that serious data models need load-script skills they do not have.
Capacity costs grow with data
Data for Analysis capacity is bought in blocks, so growing datasets push plan upgrades.
Slow apps blamed on the tool, not the model
Apps with synthetic keys and heavy expressions drag until the model is rebuilt.
Annual billing lock-in
Standard and Premium are billed annually and capacity-based plans are managed through account managers, so leaving needs planning.
Extra extensions for missing visuals
Some teams add paid extensions to get the charts they expected.
Choosing Qlik while the org standardizes on Power BI
Reviewers see market adoption moving toward Power BI.
When Qlik Sense Breaks Down
Specific scenarios where Qlik Sense fails or underperforms.
Very large apps and datasets
Calculations hit the hypercube memory limit and show out-of-calculation-memory errors.
Charts with nested IF and AGGR
Expressions without short-circuit evaluation get slow as data grows.
Scheduled reloads on unstable sources
A database restart or expired credential makes reloads fail until fixed.
Complex load scripts
Very complex scripts can leave the data load editor blank; unterminated statements load nothing.
Multi-fact data models
Shared fields create synthetic keys or circular references.
Legacy ODBC and TLS connections
Connections limited to TLS 1.0/1.1 are being cut off in newer releases.