We have a worker which we use to cache content by device type. This works well and we see the cf-cache-status:HIT header in the response. We have since added some logic which pulls content from KV based on a cookie value. When this code was deployed, the requests were no longer cached - cf-cache-status:DYNAMIC
Removing the KV get restored the cached content - is it expected that KV get’s cause this behaviour?