Opening an application to visualize charts through the hub, the visualization may fail and the error "Calculation timed out" will be printed.
Environment:
- Qlik Sense Enterprise on Windows, all versions
Resolution
NOTE: Some resource and timeout issues have been addressed as of the Qlik Sense Enterprise November 2017 12.24.4 (Patch 2) release. If this version or newer is not being used, an upgrade is required. Otherwise see below for recommendation.
There is a default timeout of 60 seconds set in the engine configuration.
If the calculation takes more than 60 seconds then the engine will abandoned the operation.
Application optimization
The recommended way to resolve this issue is to try optimizing the application or chart to prevent performance problems for the engine service. The main cause is related to the fact the most of the calculations are done on the Front End in the Objects instead in the script. By optimizing the application it is meant to move most of the calculations from the objects into the script and use pre-calculated variables and scripts.
Additionally the data model can be checked if there are not used data-island with a large number of records and a MAX(field) on that data used in a calculation field in the table causes a huge internal table due to a Cartesian product. Limiting the number of records for the data-island, the speed improves dramatically.
Verify resource availability
Verify that the servers hosting the Qlik Sense engine service have sufficient resources (CPU / Memory) to proceed with the calculation.
Modify calculation timeout
You can otherwise change the timeout.
- Open the Qlik Sense Management Console
- Open Engines
- Select the Engine to modify and click Modify
- Open the Advanced menu in menu to the right
- Modify the Hypercube time limit (seconds) The default value is 60 seconds. Setting 0 will disable the timeout but is not recommended.
- Restart the Qlik Sense Engine and Qlik Sense Service Dispatcher on all nodes after the setting was changed.
Related Content: