Workflow Health Dashboard — 2026-04-05

[github-actions]

Overview

Health scan of 181 executable workflows run at 2026-04-05T12:00Z.

Category	Count
✅ Healthy (no recent failures)	~172
⚠️ Warning (intermittent issues)	3
🔴 Critical (consistent failures)	3
📋 Stale lock files	17

Overall score: 68/100 (↓2 from 70 yesterday)

---

🔴 Critical Issues

🆕 Issue Monster — NEW REGRESSION (P1)

• Status: 5 consecutive failures since ~09:48 UTC today (was 90% success rate Apr 3)
• Error: ERR_API: Failed to fetch check runs for ref "main": route.endpoint is not a function
• Job: pre_activation
• Pattern: Started failing from run [Dependabot] Update github.com/cli/go-gh/v2 from v2.12.2 to v2.13.0 #3715 onwards; runs 📊 Daily Code Metrics Report - 2025-11-12 #3712–3714 succeeded earlier today
• Impact: Issue Monster runs every ~30 min; completely broken since 09:48 UTC
• Failing runs: §24000805890, §23999933104, §23999448495
• Priority: P1 — high-frequency workflow, sudden regression

Daily Issues Report Generator — Ongoing (P1)

• Status: Failing daily since Mar 24 (13+ days). Auto-issue: [aw] Daily Issues Report Generator failed #24703 (today's)
• Error: Agent job fails to produce firewall artifacts → no output
• Impact: No daily issue summaries generated
• Priority: P1

Duplicate Code Detector — Ongoing Codex Block (P1)

• Status: Blocked by Codex API restriction. Auto-issue: [aw] Duplicate Code Detector failed #24718 (today's)
• Error: stream disconnected before completion: This user's access to this model has been temporarily limited for potentially suspicious activity related to cybersecurity
• Impact: No duplicate code analysis running
• Note: Externally blocked; requires OpenAI policy resolution
• Priority: P1

---

⚠️ Warnings

Contribution Check — Intermittent safe_outputs failures

• Status: 50% error rate (3/6 runs on Apr 3); safe_outputs job fails despite artifact upload succeeding
• Impact: Contribution compliance checks may not post results
• Priority: P2

API Rate Limiting at 05:00–05:40 UTC (Systemic)

• Pattern: Multiple workflows hit installation rate limit concurrently; Issue Monster historically affected (6/40 runs in previous tracking period)
• Note: Issue Monster's current failure is a different error, not rate limiting
• Priority: P2

---

📋 Stale Lock Files (17 — ↑4 from 13 yesterday)

A significant churn occurred: 11 previously-stale files were recompiled, but 15 new files became stale (recent .md edits not followed by make recompile).

Newly stale (15 new since yesterday):
archie, cli-consistency-checker, codex-github-remote-mcp-test, copilot-cli-deep-research, daily-code-metrics, daily-multi-device-docs-tester, daily-team-evolution-insights, deep-report, glossary-maintainer, grumpy-reviewer, issue-monster, org-health-report, poem-bot, smoke-service-ports, update-astro

Still stale (2 carried over):
prompt-clustering-analysis, release

Action: Run make recompile to regenerate lock files after .md edits.

---

📊 Trends

• Score: 70 → 68 (↓2)
• Stale lock files: 13 → 17 (net ↑4, but 11 fixed + 15 new)
• New regressions this run: Issue Monster (route.endpoint is not a function)
• Resolved since yesterday: 11 stale lock files recompiled ✅
• Active P1 issues: Daily Issues Report ([aw] Daily Issues Report Generator failed #24703), Duplicate Code Detector ([aw] Duplicate Code Detector failed #24718), Issue Monster (new — no issue yet)

---

🔧 Actions Taken This Run

• Identified Issue Monster new regression (5 consecutive failures, new error type)
• Noted auto-issues created by workflows: [aw] Daily Issues Report Generator failed #24703 (Daily Issues Report), [aw] Duplicate Code Detector failed #24718 (Duplicate Code Detector)
• Updated stale lock file inventory (17 total, 15 new + 2 carried over)
• Updated shared repo memory for cross-orchestrator coordination

---

References:

• Issue Monster failing run: §24000805890
• Daily Issues Report failing run: §23999471243
• Workflow Health Manager run: §24001031380

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

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

[github-actions]

🍪 Issue Monster has assigned this to Copilot!

I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.

The Copilot coding agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

🍪 Om nom nom by Issue Monster · ● 180.8K · ◷