GD Cloud has a hard coded limit for SQL query execution of 30s. If the data values are not retrieved within the specified limit, the query will timeout. Usually, the root cause can vary, but in general, it could be slow datasource, a lot of data, complicated queries, stored data not optimised for performance, network latency, high load on the datasource, etc. If the amount of the data is not the cause or it is not possible to add a filter to the visualization, another possible cause could be the DB performance - e.g. high load (too many SQL queries in the queue) or the fact that the DB might need more resources or to be optimised for better performance. Just to be sure, could you please confirm, review and share the following: • The query execution times (from the database) when the filter loads were triggered. • In addition to the

Start time

,

Duration

and

SQL

, would it be possible to include and/or verify the query queue time as well as the queue priority? The idea here is to verify that the query queue time plus the execution/duration time are not longer than 30s on the database side and that the queries have the sufficient priority. • Are there any workload management rules or specific setup on the database side that might impact the query priority or the time it spends in the queue?