[safe-output-health] Safe Output Health Report - 2026-04-08

[github-actions[bot]]

Executive Summary

• Period: 2026-04-08 (last 24 hours)
• Runs Analyzed: 50 recent runs (302 run directories total)
• Workflows Active: ~15
• Safe Output Jobs Executed: 2 runs (12 individual operations)
• Safe Output Jobs Failed: 0
• Error Clusters Identified: 0
• Overall Health: ✅ Excellent — 100% success rate

Today was a very low activity day with only 2 workflow runs reaching the safe_outputs stage. Both executed flawlessly. The 2 workflow failures observed were agent-level infrastructure issues, not safe output failures.

---

Safe Output Job Statistics

Job Type	Executions	Failures	Success Rate
create_discussion	2	0	100%
create_issue	1	0	100%
add_comment	1	0	100%
upload_artifact	2	0	100%
set_issue_type	1	0	100%
create_pull_request_review_comment	2	0	100% (both skipped — not in PR context, expected behavior)
Total	12	0	100%

Note: 51 workflow runs had safe_outputs skipped because the detection job was skipped (prerequisite: agent must succeed and detection must pass).

---

Successful Safe Output Runs

Run §24136314622 — Constraint Solving POTD

• Created discussion github/gh-aw#25299: "Latin Squares & Orthogonality — Classic CSP Meets Combinatorial Design"
• Closed older discussion 🧩 Constraint Solving POTD:Product Configuration — Constraint Satisfaction at the Point of Sale #25088
• Applied 2 labels: constraint-solving, problem-of-the-day

Run §24136334286 — Smoke Copilot

• Uploaded build artifact gh-aw (9.7 MB)
• Added comment to discussion #25295
• Created discussion #25300: "copilot was here"
• Created issue #25301: "Smoke Test: Copilot - 24136334286"
• Created new parent issue group #25302
• Linked Smoke Test: Copilot - 24136334286 #25301 as sub-issue of Smoke Copilot - Issue Group #25302
• Set issue type "Bug" on Smoke Test: Copilot - 24136334286 #25301

All safe output operations completed without error.

---

Agent Failures (Out of Scope — Not Safe Output Issues)

Two workflow runs failed at the agent stage. Because safe outputs only run when the agent succeeds and detection passes, these runs never reached safe outputs. They are documented here for completeness.

Failure 1: Static Analysis Report — runner-guard image not found

• Run: §24136991460
• Workflow: Static Analysis Report (Rename "inspect" command to "mcp-inspect" #207)
• Branch: copilot/add-runner-guard-arg-to-compile
• Error: Error response from daemon: manifest unknown when pulling the runner-guard Docker image
• Root Cause: Feature branch adds a --runner-guard arg to compile, which requires a runner-guard Docker image that has not yet been published to the registry
• Impact: Agent job fails; safe_outputs job skipped
• Action: This is a development environment issue on a feature branch — no production impact. The runner-guard image needs to be published before the branch can be tested.

Failure 2: Smoke Create Cross-Repo PR — bad credentials (recurring)

• Run: §24136833219
• Workflow: Smoke Create Cross-Repo PR (Update GitHub MCP compiler to use HTTP transport by default #631)
• Error: Bad credentials - https://docs.github.com/rest when calling actions/checkout to determine default branch of githubnext/gh-aw-side-repo
• Root Cause: The PAT or app token used to access githubnext/gh-aw-side-repo has expired or is missing
• Recurring: Observed on 2026-04-06, 2026-04-07, and now 2026-04-08 (3+ consecutive days)
• Impact: Cross-repo smoke tests consistently failing; no production workflow impact

---

Error Clusters

No error clusters identified today. Zero safe output failures.

---

Recommendations

Immediate Actions

1. Renew PAT for githubnext/gh-aw-side-repo (High Priority)

   • Priority: High
   • Root Cause: Cross-repo smoke tests (Smoke Create Cross-Repo PR, Smoke Update Cross-Repo PR) have been failing for 3+ consecutive days with Bad credentials
   • Action: Rotate or renew the PAT/app token configured for the githubnext/gh-aw-side-repo side-repo access. Check the GitHub Actions secret CROSS_REPO_PAT or equivalent.
   • Pattern: cross_repo_bad_credentials (recurring since at least 2026-04-06)

2. Publish runner-guard Docker image before merging feature branch (Medium Priority)

   • Priority: Medium
   • Root Cause: copilot/add-runner-guard-arg-to-compile adds --runner-guard arg requiring a Docker image not yet published
   • Action: Either publish the image to the registry or mock the pull in CI for the feature branch. This is a dev workflow issue, not production.

---

Historical Context

Recent daily health trend (last 10 days)

Date	Runs	SO Executed	Failures	Health
2026-03-29	—	—	—	Some errors (patterns logged)
2026-04-02	—	—	7	API rate limit burst
2026-04-04	46	33	0	✅ Excellent
2026-04-05	198	49	0 (1 soft)	✅ Excellent
2026-04-06	—	—	0	✅ Healthy (cross-repo creds warning)
2026-04-07	45	25	1	⚠️ 1 API rate limit (concurrent burst)
2026-04-08	50	2	0	✅ Excellent

Trends

• Safe output error rate: Trending toward zero — 5 of the last 6 days had 0 hard failures
• Most reliable operations: create_discussion, create_issue, add_comment — all 100% over the last week
• Most common recurring issue: cross_repo_bad_credentials — active for 3+ days without resolution
• API rate limit risk: Last occurred 2026-04-07; risk remains when multiple workflows fire concurrently

---

Metrics and KPIs

• Overall Safe Output Success Rate (today): 100%
• Most Reliable Job Type: All types (no failures today)
• Most Problematic (historical): create_issue under API rate limit conditions
• Consecutive Days Without Hard Failures: 2 (2026-04-07 had 1 rate limit failure; 2026-04-08 clean)

---

Next Steps

• Renew/rotate PAT for githubnext/gh-aw-side-repo cross-repo access (3+ day outage)
• Publish runner-guard Docker image before landing copilot/add-runner-guard-arg-to-compile
• Monitor for API rate limit bursts — concurrent scheduling risk remains

References:

• §24136334286 — Smoke Copilot (successful)
• §24136314622 — Constraint Solving POTD (successful)
• §24136833219 — Smoke Create Cross-Repo PR (agent failure, recurring)

Generated by Safe Output Health Monitor · ● 333.9K · ◷

• expires on Apr 9, 2026, 1:20 PM UTC

[github-actions[bot]]

This discussion has been marked as outdated by Safe Output Health Monitor.

A newer discussion is available at Discussion #25477.