Repository navigation
[health] Smoke Update Cross-Repo PR: 100% failure rate on schedule (6/6 consecutive failures) #22241
Closed as not planned
Description
Overview
The Smoke Update Cross-Repo PR workflow is experiencing a complete outage on scheduled runs, with 0 out of 6 scheduled runs succeeding over the past 7 days (March 15–22, 2026).
Failure Summary
| Metric | Value |
|---|---|
| Workflow | smoke-update-cross-repo-pr |
| Success rate (7d, schedule) | 0/6 (0%) |
| First observed failure | Run #281 (~Mar 15) |
| Latest failure | Run #287 (2026-03-22T01:04) |
| Pattern | All scheduled runs fail; PR-triggered runs are skipped |
| Priority | P1 — Full outage |
Recent Run History
| Run # | Event | Result | Date |
|---|---|---|---|
| #287 | schedule | ❌ failure | 2026-03-22T01:04 |
| #285 | schedule | ❌ failure | 2026-03-21T13:00 |
| #283 | schedule | ❌ failure | 2026-03-21T01:03 |
| #281 | schedule | ❌ failure | 2026-03-20T13:00 |
| #286, #284 | pull_request | ⏭ skipped | 2026-03-21 |
References: Run #287 — Latest failure
Context
The companion workflow Smoke Create Cross-Repo PR is mostly healthy (5/6 success, 83%). The update step specifically is failing, suggesting an issue with:
- PR state (PR created by smoke-create may already be merged/closed before smoke-update runs)
- Label resolution in the update step
- Cross-repo permissions for updating PRs
- Timing mismatch between create and update schedules
Previous tracking in shared-alerts noted "Label resolution failure on latest runs" for this workflow pair.
Suggested Investigation
- Check logs of run [UPDATED] Update Issue Test - Processed by Codex #287: https://github.com/github/gh-aw/actions/runs/23392658504
- Compare with
smoke-create-cross-repo-prsuccess logs to see if the PR being updated still exists - Check if labels used in update step have been renamed or deleted
- Verify cross-repo token permissions are still valid
- Consider whether the create/update workflow pair needs better coordination (e.g., passing PR number between runs)
Impact
- Smoke testing for cross-repo PR update functionality is completely disabled
- Any regressions in
gh awcross-repo PR update features will go undetected - Related:
smoke-create-cross-repo-pris still passing (83%) so create path is functional
Note
**🔒 Integrity filter blocked 13 items**
The following items were blocked because they don't meet the GitHub integrity level.
- #unknown
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - get_job_logs
get_job_logs: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - Workflow Health Dashboard — 2026-03-21 | Score: 74/100 ↑8 #22108
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - [Contribution Check Report] Contribution Check Report — 2026-03-22 #22236
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - [plan] Make Smoke Update Cross-Repo PR self-healing: auto-recreate pr-branch when missing #22233
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - [plan] EP006: Fix Smoke Multi PR add_comment to use item_number instead of target=triggering #22232
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - [plan] EP022: Add branch existence pre-flight check to push_to_pull_request_branch handler #22231
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - [aw] Smoke Codex failed #22228
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - 🔍 Multi-Device Docs Testing Report - 2026-03-22 #22226
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - [PR Triage Report] PR Triage Report - 2026-03-22 #22212
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - [cli-tools-test] 6 workflows fail compilation:
toolsets: [all]requires missingvulnerability-alerts: readpermission #22207list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - [plan] Fix CRITICAL toolName shell injection in mcp_setup_generator.go (unfixed since run 26) #22203
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - [plan] Fix YAML injection via unquoted cache name/key/path fields in generateCacheSteps (cache.go) #22202
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
To allow these resources, lower min-integrity in your GitHub frontmatter:
tools:
github:
min-integrity: approved # merged | approved | unapproved | noneGenerated by Workflow Health Manager - Meta-Orchestrator · ◷
- expires on Mar 23, 2026, 7:32 AM UTC
Activity
github-actions commentedon Mar 23, 2026
Status Update — 2026-03-23T07:38Z · §23426422007
Failure continues. Now 8+ consecutive scheduled failures with no recovery in sight.
Updated Run History
Success rate (scheduled): 0/7+ (0%) since at least Mar 15.
Context
The companion Smoke Create Cross-Repo PR workflow is intermittently failing too — run #293 failed on 2026-03-23T01:10, run #285 failed on 2026-03-21T13:06 (~75% success rate). This suggests a broader issue with the cross-repo PR pair rather than just the update step.
Recommendation: This issue has been open for >24 hours with no change in status. Consider escalating to manual investigation of the cross-repo PR state and label configuration.
Note
🔒 Integrity filter blocked 2 items
The following items were blocked because they don't meet the GitHub integrity level.
get_job_logs: has secrecy requirements that agent doesn't meet. The agent is not authorized to access [secret]-scoped data.search_issuessearch_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:github-actions commentedon Mar 23, 2026
This issue was automatically closed because it expired on 2026-03-23T07:32:54.485Z.