[BUG] Routine GitHub issues.labeled trigger stopped firing ~July 2026 — no sessions created, fresh routines also affected
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
A routine with a GitHub event trigger on issue labeled (label filter: claude) stopped firing entirely around July 2026. It had worked reliably for weeks before that with no configuration changes on my side.
Adding or re-adding the label to an issue creates no session at all — nothing appears in the routine's run list at claude.ai/code/routines, so this is not the "session refuses prompt" regression from #78032.
Creating a brand-new routine from scratch with the same trigger (repo, issue labeled event, label filter) also never fires.
The Claude GitHub App is installed on the repository and shows as connected.
The trigger option (custom event → issue labeled with label filter) is still offered in the routine creation UI, but I note the docs at code.claude.com/docs/en/routines now only list Pull request and Release as supported events.
Possibly related: #81455 (issue-labeled trigger with label filter fails on update), #72290.
What Should Happen?
a new session starts for the matching event, as it did until ~July 2026.
Error Messages/Logs
Steps to Reproduce
Steps to reproduce
- Create a routine at claude.ai/code/routines with a GitHub event trigger: issue labeled, label filter claude, on a repo with the Claude GitHub App installed.
- Add the claude label to any issue in that repo.
- Observe: no session is created; the run list stays empty.
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
claude code web
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Non-interactive/CI environment
Additional Information
_No response_
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗