Safe Output Health Report - 2026-03-27

[github-actions[bot]]

Executive Summary

• Period: Last 24 hours (2026-03-27)
• Workflow Runs Analyzed: 166
• Unique Workflows Active: 61+
• Runs with Safe Output Jobs: 133
• Safe Output Messages Processed: 24 (across 7 accessible runs)
• Safe Output Hard Failures: 0
• Safe Output Success Rate: 100%
• Warnings: 2 (non-fatal, recurring patterns)
• Safe Outputs Blocked by Detection Failure: 4

Overall system health is stable. No new error patterns observed. Two recurring low-severity warnings continue. 100% success rate maintained for the second consecutive day.

---

Safe Output Job Statistics

Job Type	Executions	Failures	Warnings	Success Rate
noop	2	0	0	100%
add_comment	3	0	0	100%
add_labels	1	0	0	100%
create_discussion	2	0	1 (labels missing)	100%
create_issue	2	0	0	100%
create_pull_request_review_comment	4	0	0	100%
submit_pull_request_review	2	0	1 (no PR context)	100%
missing_data	1	0	0	100%
update_pull_request	1	0	0	100%
dispatch_workflow	1	0	0	100%
set_issue_type	1	0	0	100%
add_reviewer	1	0	0	100%
Custom (send_slack_message, test_environment)	2	0	0	N/A (custom)

Note: Only 7 of 133 runs had accessible safe output logs (permission restrictions on others). Counts reflect what was observable.

---

Warnings Observed

Warning 1: Missing Repository Labels (EP_LABELS_MISSING) — 4th Consecutive Day

• Run: §23647040380 — Constraint Solving — Problem of the Day
• Job: create_discussion
• Message: Could not find label IDs for: constraint-solving, problem-of-the-day
• Impact: Discussion created successfully (🧩 Constraint Solving POTD:Open-Shop Scheduling #23233), but labels were not applied.
• Severity: Low (non-fatal; main operation succeeds)
• Pattern: First observed 2026-03-24. Now 4 consecutive days.

Root Cause: Workflow frontmatter specifies labels constraint-solving and problem-of-the-day that do not exist in the repository.

Warning 2: PR Review Submitted Without PR Context (EP015) — Recurring

• Run: §23647052002 — Smoke Copilot
• Job: submit_pull_request_review
• Message: No review context set - cannot submit review
• Impact: PR review not submitted; other 7 messages succeeded. Overall run: success.
• Severity: Low (warning-only; fails gracefully)
• Pattern: Recurring on schedule-triggered Smoke Copilot runs (previously observed 2026-03-16, 2026-03-20, 2026-03-26).

Root Cause: When Smoke Copilot runs on a schedule trigger (not a pull request event), the agent generates submit_pull_request_review output, but there is no PR context for the handler to target.

---

Runs Where Safe Outputs Were Blocked by Detection Failure

These are out of scope for safe output health but reduce agent output availability:

Workflow	Run	Reason
Delight	§23645311151	Detection failure → safe_outputs skipped
Smoke Gemini	§23646700407	Detection failure → safe_outputs skipped
Smoke Update Cross-Repo PR	§23647247050	Agent + detection failure
Smoke Create Cross-Repo PR	§23647492346	Agent + detection failure

The detection failures for Delight and Smoke Gemini are consistent with EP024 (Copilot detection model not producing THREAT_DETECTION_RESULT output), first observed 2026-03-26.

---

Recommendations

Low Priority — Create Missing Repository Labels

• Issue: constraint-solving and problem-of-the-day labels are missing from the repository.
• Affected Workflow: Constraint Solving — Problem of the Day (daily schedule)
• Impact: 4 consecutive days with label application failure (non-fatal)
• Action: Either:
  1. Create labels in the repository: constraint-solving, problem-of-the-day
  2. Remove them from the workflow's frontmatter label configuration
• Effort: Small

Low Priority — Fix Smoke Copilot PR Review Context for Schedule Runs (EP015)

• Issue: Schedule-triggered Smoke Copilot generates submit_pull_request_review output despite no PR context.
• Impact: Warning logged; run succeeds. Recurring ~4x/week.
• Action: Update agent prompt to only generate PR-specific safe outputs when triggered by a pull request event, not schedule.
• Effort: Small

---

Historical Context and Trends

30-Day Success Rate Trend

Date	Success Rate	Hard Failures	Notable
2026-02-21	88.9%	2	EP001: git branch resolution bug
2026-02-24	85.7%	3	EP005: add_comment permission error
2026-02-25	94.1%	0	EP006: context mismatch
2026-03-13	89.7%	0	EP012: PR review comment validation
2026-03-16	81.8%	4	EP006, EP015, EP016
2026-03-17	93.3%	1	EP017: GitHub App 404
2026-03-18	83.3%	1	EP018: protected path prefix
2026-03-20	90.2%	4	EP006, EP015, EP016, EP021
2026-03-22	93.8%	2	EP006, EP022
2026-03-24	96.97%	1	EP022, EP021
2026-03-25	100%	0	Clean
2026-03-26	100%	0	Clean
2026-03-27	100%	0	Clean (3rd consecutive)

Active Recurring Patterns

Pattern ID	Name	Days Active	Status
EP_LABELS_MISSING	Missing labels for constraint-solving-potd	4 days	Low severity, non-fatal
EP015	Smoke Copilot PR review no context (schedule)	Recurring (~weekly)	Warning only
EP024	Detection model THREAT_DETECTION_RESULT missing	2 days	Blocks safe_outputs (out of scope)

---

Next Steps

• Create missing labels constraint-solving and problem-of-the-day in the repository (or update workflow config)
• Update Smoke Copilot agent prompt to avoid PR-specific outputs on schedule triggers
• Monitor EP024 (detection model format failure) — if it persists, escalate as it blocks valid agent outputs

References:

• §23647052002 — Smoke Copilot (EP015 warning)
• §23647040380 — Constraint Solving POTD (EP_LABELS_MISSING)
• §23646156582 — Smoke Claude (8/8 success)

AI generated by Safe Output Health Monitor · history

• expires on Mar 28, 2026, 1:17 PM UTC

[github-actions[bot]]

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

A newer discussion is available at Discussion #23354.