Skip to main content

Query caching

Control when a query executes by configuring its cache settings.

tip

Cached queries are limited to 20GB. Results of a query that exceed this limit will be discarded.

When the cache is disabled, your query will execute with every run of your project. The following configuration options are available when caching is enabled:

  • On initial app load: The query will only execute and update the cache when a user first loads (or refreshes) an app. Any other run of the project will use the cached values of the query.

  • On scheduled run: The query will only execute and update the cache during a schedule run of the project or a run triggered by the Hex API. Any other run of the project will use the cached values of the query.

  • On parameter change (always true): If a user changes an input parameter that is used in a SQL query, that query will always run.

As an example, the screenshot below demonstrates a query that will only execute if a user changes the variable, countries , or during a scheduled project run on Tuesday at 9:03am. At all other times, the project will use the cached values of this query.