When looking into first paragraph here - https://directus.io/docs/configuration/cache - we can read: > Enabling this will cache the output of requests (based on the current user and exact query parameters used) into configured cache storage location. Although, the cache is not based on query parameters so there's no cache buster mechanism that will work. As can be seen [here](https://github.com/directus/directus/blob/main/api/src/utils/get-cache-key.ts#L23-L29), cache is based on: - Directus Version - Current User ID - Request Path (excluding query) - Directus Query parameters (not all URL query parameters) - User IP, if required by the Policy / Role