[health] Smoke Update Cross-Repo PR: continued 100% schedule failure (tracking after #22241 expired)

[github-actions]

Overview

The Smoke Update Cross-Repo PR workflow continues to fail on all scheduled runs. The previous tracking issue #22241 was auto-closed by expiry at 08:58 UTC on 2026-03-23, but run #301 (scheduled at 13:02 UTC the same day) also failed — leaving the outage untracked.

Current Status

Metric	Value
Workflow	smoke-update-cross-repo-pr
Schedule success rate (7d)	0% (0/8+ consecutive failures)
Previous issue	#22241 (closed by expiry 2026-03-23T08:58Z)
Latest known failure	Run #301 — 2026-03-23T13:02Z
Pattern	All scheduled runs fail; PR-triggered runs skip

Recent Failure History

Run #	Event	Result	Date
#301	schedule	❌ failure	2026-03-23T13:02Z
#292	schedule	❌ failure	2026-03-23T01:04Z
#288	schedule	❌ failure	2026-03-22T13:01Z
#287	schedule	❌ failure	2026-03-22T01:04Z
#285	schedule	❌ failure	2026-03-21T13:00Z
#283	schedule	❌ failure	2026-03-21T01:03Z

Pattern Analysis

The workflow consistently uses create_issue and push_to_pull_request_branch on failure, confirming it runs far enough to detect the error. Tool usage per run: ~10 get_pull_request calls, ~4 label_agent calls — the agent reaches the update step, then fails.

Root cause hypothesis: The PR created by smoke-create-cross-repo-pr may be merged/closed before smoke-update-cross-repo-pr runs, causing the update step to fail on a non-existent PR. The create workflow has 83% success rate, further supporting a timing/state mismatch.

Suggested Investigation

1. Review run Safe discussions, pull request reviews and better errors  #301 logs: https://github.com/github/gh-aw/actions/runs/23438621851
2. Check if the cross-repo PR is still open at the time the update workflow runs
3. Verify label resolution in the update step
4. Consider adding existence check for the target PR before attempting update

Impact

• Cross-repo PR update smoke testing completely disabled for 8+ consecutive schedule runs
• Any regression in gh aw cross-repo PR update features will go undetected

Detected by Agent Performance Analyzer - Meta-Orchestrator

Note

🔒 Integrity filter blocked 6 items

The following items were blocked because they don't meet the GitHub integrity level.

• upload-asset safe output doesn't work for private repos #22510 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• mark_pull_request_as_ready_for_review handler uses REST API which cannot undraft PRs #22469 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• create_code_scanning_alert may be broken #22430 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• Option staged: true does not work within individual safe outputs #22409 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• conclusion job reports missing agent_output.json instead of the actual engine failure #22380 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• Missing model/version in activation run details #22404 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 | none

Generated by Agent Performance Analyzer - Meta-Orchestrator · ◷

• expires on Mar 25, 2026, 9:11 PM UTC

[github-actions]

Status Update — 2026-03-24T12:15Z · §23488413680

Failure continues. Run #316 (2026-03-24T00:57Z) confirms the outage is ongoing — now 12+ consecutive scheduled failures over 9+ days (since ~Mar 15).

Updated Run History

Run #	Event	Result	Date
#316	schedule	❌ failure	2026-03-24T00:57Z
#301	schedule	❌ failure	2026-03-23T13:02Z
#292	schedule	❌ failure	2026-03-23T01:04Z
#288	schedule	❌ failure	2026-03-22T13:01Z
#287	schedule	❌ failure	2026-03-22T01:04Z
#285	schedule	❌ failure	2026-03-21T13:00Z
#283	schedule	❌ failure	2026-03-21T01:03Z

Schedule success rate (7d+): 0/12+ (0%)

Context

All recent PR-triggered runs are skipped (activation conditions not met), so there is no interference — the scheduled runs are the only actual executions and all are failing.

This issue expires 2026-03-25. If not resolved before then, a follow-up tracking issue will be needed. Escalation is recommended given 9+ days with no fix.

Generated by Workflow Health Manager - Meta-Orchestrator

Generated by Workflow Health Manager - Meta-Orchestrator · ◷

[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 · ◷