You control the trade-off between reuse and freshness. Set a time to live (TTL) that matches how long your application can use an older result.
Database writes do not automatically refresh cached results. A cached response can remain available until it expires, is evicted, or you clear the cache. Expiry does not trigger a background refresh: the next eligible miss retrieves the result from the database.
In Result Cache Settings, enable caching for a database profile and set the lifetime, cache memory and entry limits, maximum query length, and maximum result size. Clear Cache discards stored results before their lifetime ends.
Large result sets and queries with little reuse may not benefit from caching.