Issue Summary

There are cache-key recognition issues with the caching mechanism, where self-hosted runners fail to recognize caches that are acknowledged by cloud runners, despite both targeting the same cache-key with identical cache definitions.

Steps to Reproduce

1. Set up a Pipelines with two steps: one running on a self-hosted runner and the other on a cloud runner.
2. Define key-based caching intended for use by both steps in the pipeline.

Expected Results

Both self-hosted and cloud runners should recognize and utilize the same cache, identified by a consistent cache key

Actual Results

Self-hosted and the cloud runners use different caches

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available