Cache indexing lag / API propagation delay
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
There's a brief delay between cache save completion and its availability in cache queries / restore cache.
We are using actions/cache v4.2.2 and seeing an unusual lag between cache save and it's availability in cache queries using gh cache list query or restore cache action.
It took about 4 minutes for the cache to show up in API results/cache UI and we are having to retry the workflow job every time. Can this be investigated please?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are named. Start by reproducing a workflow with actions/cache v4.2.2, then compare cache save completion with visibility in gh cache list and the restore cache action. Done means the propagation delay is explained and the cache becomes reliably available without retrying the workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- api, ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100