Workflow: Issue Monster (issue-monster)
Priority: P1
First seen: 2026-04-05T09:48 UTC (run #3715)
Status: 5+ consecutive failures (runs #3715–#3719 as of this report)

Failure Pattern

The workflow started failing in its pre_activation job with:

ERR_API: Failed to fetch check runs for ref "main": route.endpoint is not a function

This error began at run #3715 (~09:48 UTC) after 3 successful runs earlier in the day (#3712–#3714 at 07:31–08:49 UTC).

Timeline

Error Details

• Job: pre_activation
• Error message: ERR_API: Failed to fetch check runs for ref "main": route.endpoint is not a function
• Step: "Checking CI checks on ref: main (github/gh-aw)"
• Example failing run: §24000805890

Analysis

The error route.endpoint is not a function typically indicates a JavaScript SDK method call issue — either:

1. A breaking change in the @octokit/rest or @actions/github SDK
2. A recent change to the actions/setup JavaScript code that broke the check_runs API call
3. A GitHub API endpoint change

The error occurs in the CI check validation step, which calls the GitHub Checks API to verify CI status before activating.

Note: The lock file for issue-monster is also listed as stale (.md modified after .lock.yml), which may be related.

Suggested Investigation

1. Check if any recent commits changed actions/setup/js/*.cjs files, especially the check-runs logic
2. Verify the Octokit API call for check_runs in the pre-activation script
3. Compare the issue-monster.lock.yml and issue-monster.md to see what changed
4. Check if other workflows using CI check validation are also failing

Impact

Issue Monster runs every ~30 minutes. With 5+ consecutive failures, it has been non-functional for 2+ hours, missing approximately 5 issue processing cycles.

References:

• Failing run: §24000805890
• WHM detection run: §24001031380

Generated by Workflow Health Manager - Meta-Orchestrator · ● 1.4M · ◷

• expires on Apr 6, 2026, 12:05 PM UTC