actions / actions/cache

Unable to reserve cache (actions/cache/save@v5)

Open
#1,707 1 comment 11 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
5.6k
Forks
1.6k
PR merge metrics
No merged PRs in 30d

Description

When using actions/cache/save@v5 to rewrite the existing cache, the action ends up with the following error:

Failed to save: Unable to reserve cache with key XXX, another job may be creating this cache.
Warning: Cache save failed.

I've seen similar issues like #342, but when you look at the documentation of https://github.com/actions/cache/tree/main/save#case-1---where-a-user-would-want-to-reuse-the-key-as-it-is, the example clearly shows that the cache key CAN be reused and overwritten.

Could someone explain if it's something I am doing wrong or if it's something that is being actively overlooked in this action?

(I am almost 100% sure that there is no race condition on my side as I only use 1 workflow with a single job and I am explicitly using actions/cache/restore and actions/cache/save.)

Thanks!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the actions/cache/save@v5 and actions/cache/restore usage described in the issue, then compare it with the linked save documentation example for reusing a key. Reproduce the failure in a single-job workflow and determine whether key reuse is supported; done means the behavior is explained and the documentation or action behavior has a clear resolution.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, typescript
Domain
ci-cd
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.