Cache key is ignored on self-hosted env

[Kristina Argirova]

hi, community. Has anyone faced this issue?

I have two steps - one is running on the bitbucket and one - on self-hosted env. Both are using the same cache configuration. In the first case, the cache is downloaded with a key, in the second step - the key is ignored. 

Here is the cache configuration used in both cases:

caches:
  node-modules-cache:
    key:
      files:
        - package-lock.json
    path: node_modules

The step on self-hosted env fails because it cannot load the cache with a key 

Cache "node-modules-cache: node_modules": Downloading Cache "node-modules-cache: node_modules": Not found

If I change the cache configuration to not use the key, then both steps pass successfully:

caches:
  node-modules-cache:
    path: node_modules

[Brant Schroeder]

@Kristina Argirova welcome to the Atlassian community

This is usually caused due to a difference in the cloud and local environments.  You should clear local cache and try again.