Restore Cache and Save Cache steps don't currently indicate whether a cache was actually restored or saved, the step reports success either way. The only related setting, failIfKeyNotFound, fails the whole stage on a miss, which isn't practical to use just for visibility.

Harness Support confirmed hit/miss reporting exists for the newer "restore from Harness" cache step, but not for S3/GCS-backed cache steps on self-hosted infrastructure. We'd like the same reporting extended to those step types, including how much was actually restored. This would let us track time and cost savings from cache restores per pipeline, and identify which pipelines aren't using cache effectively so we can take action