We redesigned the invocation list on the Build Cache overview page to make it easier to understand whether your cache is working.
New: Cache status column
The old Cache hit rate percentage has been replaced with a Cache status label that tells you at a glance what your cache was doing on each invocation. The status is based on the remote cache upload/download ratio and the benchmark phase:
- In progress: Build is still running. Status will update when it completes.
- Baseline: Reference run without cache, used as a benchmark baseline for future comparisons.
- Warming up: Cache is still being populated. Duration improvements aren’t representative yet.
- Healthy: Cache is being reused as expected. Technically speaking this status means that the invocation downloaded more from the build cache than it uploaded into it. If you want to check whether Build Cache is saving you time, these are the invocations to look at.
- Low reuse: Most data was uploaded rather than reused from cache. Can happen after a build tool update (one-off) or due to a config issue (persistent).
- No activity: No cache data was transferred. The command may not be cacheable, or cache may be turned off. Worth to look into if you expect the command to use build cache, as this might be due to configuration issue.
Hover any status label to see the exact download and upload amounts.
Why the change?
The cache hit rate percentage was confusing because it included local cache hits from the build tool (e.g. Gradle’s own cache), making it unreliable as an indicator of whether Build Cache was actually helping. The new status labels are derived from remote cache data only, giving you a clearer picture.