š¤ ci: Auto-Cleanup fails every run with an invalid Anthropic API key
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, typescript
- Domain
- ci-cd
Research direction
Read .github/workflows/auto-cleanup.yml and inspect its schedule and AUTO_CLEANUP_ANTHROPIC_API_KEY secret reference. The reported failure is an invalid secret, which only a repository admin can fix by replacing the key or disabling the schedule; the payload identifies no code change a contributor can make to resolve it.
Written by the indexing model from the issue text.
Description
Problem
The scheduled Auto-Cleanup workflow (.github/workflows/auto-cleanup.yml) fails on every run. The last 200 runs, back to at least 2026-09-20, all failed. It runs every 4 hours.
The Cleanup with xum step fails with:
APICallError [AI_APICallError]: invalid x-api-key
error: { type: 'authentication_error', message: 'invalid x-api-key' }
Example: run 40043118178 (2026-10-24 00:04Z). The workflow reads the key from the AUTO_CLEANUP_ANTHROPIC_API_KEY repository secret. The secret is set (the workflow's "missing key" skip does not trigger), but Anthropic rejects it.
Fix
Only a repository admin can fix this:
- Option A: replace
AUTO_CLEANUP_ANTHROPIC_API_KEYwith a valid key. - Option B: if the auto-cleanup PRs are no longer wanted, turn off the schedule (one
on:change in the workflow), so it stops failing every 4 hours.
No code change in the repo fixes the key itself.
Generated with xum ā¢ Model: anthropic:claude-opus-5-5 ā¢ Thinking: high
- Dominant language
- TypeScript
- Stars
- 2.1k
- Forks
- 140
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 952
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing 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.
More from coder/xum
-
š¤ fix: Daytona startAndWait can start a sandbox after its deadline and then report a timeoutOpen
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
coder/xum#7358 Ā· 3 comments Ā·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
coder/xum#7283 Ā· 1 comment Ā·
Maintainers usually reply within 1 day
Similar issues
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 86/100
lingdojo/kana-dojo#33145 Ā· 1 comment Ā· 5 reactions Ā·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
code-yeongyu/senpi#4278 Ā·
Maintainers usually reply within 1 day
-
[Bug] Activity | The activity list ignores taskIds and returns the activities of every taskPossibly taken @NdekoCode claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ever-co/ever-gauzy#11469 Ā·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
griffinwork40/agent-afk#4408 Ā·
Maintainers usually reply within 1 day