I have an app inside a Qlik Cloud tenancy that has been failing for days. This app grabs data from a Snowflake table. The error I got is something about the query hitting the timeout (600 seconds or 10 minutes).
I have confirmed in Snowflake as well that the particular query does take 11-12 mins to complete. Since optimization on Snowflake side will take some time to plan and implement, as an immediate workaround we increased the timeout configuration in Qlik Cloud side by editing the Snowflake connection Query timeout field from 600 to 900 seconds.
However, when we executed the app, it is still failing and the log says it timed out after 600 seconds, basically not respecting the updated value that is 900 secs.
Does the timeout update in the connector actually work if it’s more than 600? Are there any ways to check or fix this timeout issue?
Split the request in many parts using a datetime field or something else and them store in Qlik as parquet files and after that build the Qlik Sense App would be acceptable (like paged APIs)?
With this approach you could build fast request (less them 600) in several steps and them consolidate everything inside Qlik
Split the request in many parts using a datetime field or something else and them store in Qlik as parquet files and after that build the Qlik Sense App would be acceptable (like paged APIs)?
With this approach you could build fast request (less them 600) in several steps and them consolidate everything inside Qlik
