[GitHub integration] pull_request.labeled does not start a routine; Run now works

Screenshot

_No response_

What were you trying to do?

Start a Claude Code routine automatically from a GitHub "Pull request: labeled" event on a private repository covered by the Claude GitHub App. Routine trig_01U28tzXPm72vUWKiCUf1HRv should start a session when the label "handoff" is added to a specific draft PR.

What happened instead?

No automatic run ever appeared in the routine history. GitHub recorded five label additions on 2026-10-10 at 18:00:25, 18:09:39, 18:19:55, 18:22:49 and 18:27:00 UTC, all after the routine was created (17:57:59 UTC). Same result with four filters, with the Labels filter only, and with no filters at all.

A manual "Run now" at about 18:45 UTC did start a session normally, so the routine itself works. Only the GitHub event trigger never fires. Full details are in the Diagnostics section below.

Diagnostics

Filed from: GitHub settings for Claude Code on claude.ai
Report code: GH-FWTRH2
Page: claude.ai/customize/connectors/integration-github
Client: web

Routine ID: trig_01U28tzXPm72vUWKiCUf1HRv (created 2026-10-10T17:57:59Z, active)
Trigger: GitHub event "Pull request: labeled" on a private repository
GitHub installation ID: 169425332

On 2026-10-10, GitHub recorded five label additions on a draft PR at 18:00:25, 18:09:39, 18:19:55, 18:22:49 and 18:27:00 UTC, all after the routine was created. No automatic run appeared in the routine history. Tests used four filters (Labels / Head branch / Is draft / Is merged), then Labels only, then no filters, on the same routine; the original filters were restored and re-read after the tests.

The Claude GitHub App covers All repositories, with read/write permissions for pull requests, issues and repository hooks. No pending permission banner is visible. The claude.ai repository checker reports that cloud sessions can work in the repository.

One manual Run now at approximately 18:45 UTC started a session, which stopped at the expected missing-label guard. No usage or blocking message was displayed.

Please inspect the saved trigger subscription, event delivery/processing and applicable trigger limits for this routine and these timestamps.