Workflow Health Issue
Workflow: PR Description Updater (pr-description-caveman)
Trigger: pull_request: [closed] (when PR is merged)
Priority: P1
Run: https://github.com/github/gh-aw/actions/runs/28997022503
Failure Pattern
- Failure rate: 19/20 runs AR (95%) since July 1, 2026
- Status: Consistently
action_required — only 1 success in 20 runs
- Engine: Copilot (uses sub-agents)
- Trigger pattern: Fires on every merged PR
Impact
This workflow rewrites merged PR descriptions with structured summaries optimised for downstream agentic analysis. With 95% failure rate, PR descriptions are not being updated, degrading downstream agentic context quality.
Observed Failure
All recent runs (Jul 4–9) result in action_required. The workflow uses strict: true with sub-agents for chunked diff processing. Possible causes:
- Safe-output validation failure (produces no safe outputs)
- Sub-agent model resolution issue (similar to other Copilot sub-agent failures)
strict: true causing false-positive failures when PR has no description to update
- Token/timeout issues with large diffs
Example Runs
Suggested Investigation
- Check if safe-output
update-pull-request is being called before workflow exits
- Review sub-agent model resolution (may be hitting same Codex 404 pattern)
- Consider: is
strict: true appropriate here if some PRs legitimately need no update?
- Check if the PR diff chunking logic is causing issues with small/auto-generated PRs
Related Issues
Generated by 🏥 Workflow Health Manager - Meta-Orchestrator · 86.5 AIC · ⌖ 11.8 AIC · ⊞ 7.7K · ◷
Workflow Health Issue
Workflow: PR Description Updater (pr-description-caveman)
Trigger:
pull_request: [closed](when PR is merged)Priority: P1
Run: https://github.com/github/gh-aw/actions/runs/28997022503
Failure Pattern
action_required— only 1 success in 20 runsImpact
This workflow rewrites merged PR descriptions with structured summaries optimised for downstream agentic analysis. With 95% failure rate, PR descriptions are not being updated, degrading downstream agentic context quality.
Observed Failure
All recent runs (Jul 4–9) result in
action_required. The workflow usesstrict: truewith sub-agents for chunked diff processing. Possible causes:strict: truecausing false-positive failures when PR has no description to updateExample Runs
Suggested Investigation
update-pull-requestis being called before workflow exitsstrict: trueappropriate here if some PRs legitimately need no update?Related Issues