[aw-failures] [aw] Failure Investigator Report — 2026-08-20 01:11 UTC (6h)

[github-actions]

Executive summary

Fix the "activation" artifact name rejection now — it took down the entire smoke-test fleet at 23:48 UTC. GitHub's artifact API started rejecting Create Artifact Container calls with The artifact name activation is not valid, killing at least 3 confirmed smoke workflows simultaneously, with ~20 more failed run IDs in the same window likely sharing the same cause. No existing open issue tracks this exact signature, so a new parent + sub-issue is opened below.

Two agent-CLI failures (Copilot CLI, Pi CLI) were also seen but carry no distinguishing signature beyond generic exit code 1 — logged for visibility only, no action taken.

Failure cluster table

Cluster	Severity	Workflows	Representative run	Comparator run	Signature
Artifact name rejection	P0	Smoke OTEL, Smoke Copilot Small, Smoke Copilot MAI (+ likely more of the 25 unlabeled failed IDs in the same window)	§32314806549	§32314804312	Create Artifact Container failed: The artifact name activation is not valid
Agent CLI exit 1 (no signature)	P2	Daily Go Test Parallelizer, Auto-Triage Issues	§32318213755	§32317125168	Generic Agent execution exited with code 1 — no rate-limit/network/proxy signature found

Evidence

Artifact-rejection root cause (audit + audit-diff)

agentic-workflows audit on run 32314806549 returned:

##[error]Create Artifact Container failed: The artifact name activation is not valid.
Request URL https://pipelinesghubeus12.actions.githubusercontent.com/.../artifacts?api-version=6.0-preview

Failure occurs in the activation job at the "Upload activation artifact" step — before the agent job ever starts (0 tokens spent).

audit-diff between §32314806549 and §32314804312 (Smoke Copilot Small vs Smoke Copilot MAI, both failed): zero firewall/domain anomalies, zero token usage on both — confirms both runs died identically at the same infra step, not from workflow-specific drift. This is one systemic cause, not three separate bugs.

Agent CLI failures — insufficient evidence

Audit of §32318213755 (Daily Go Test Parallelizer) surfaced only Agent execution exited with code 1 with no rate-limit, proxy, timeout, or auth signature in usage/rate-limit logs. Auto-Triage Issues run §32317125168 uses a different CLI (Pi) entirely — not the same signature, so not clustered together. Both P2, no action taken this cycle.

Existing issue correlation

• No match for the artifact-rejection cluster. Closest existing issue is [aw-failures] Smoke Copilot Sub Agents: 'evals' artifact not found — full run failure #53262 ("'evals' artifact not found — full run failure") but that's a missing artifact at read time, not an API rejection of the artifact name at creation time — different failure mode, left open and cross-referenced only.
• No other open agentic-workflows issue ([aw-failures] [P0] Cloud Hypervisor guest network never comes up — full egress blackout kills sandbox runs across engines #53935, [aw-failures] [P0] Daily Evals Feature Report: Execute Codex CLI hangs with total egress blackout (18m36s, zero calls to any domain) #53130, [aw-failures] [P0] Sentry/Grafana MCP servers silently omitted when secrets missing — blocks Daily AIC Consumption Report #52726, [aw-failures] [P1] Anthropic proxy connection-refused/retry-exhaustion now hitting 3 workflows after ~10 retries #52459, [aw-failures] [P1] PR Sous Chef: Start DIFC Proxy step fails with no captured root cause #52502, [aw-failures] [P1] Design Decision Gate hangs silently mid-tool-use in Claude Code CLI step #53619, [aw-failures] safe_outputs job hard-fails entire batch on one non-retryable error #53263, [aw] [aw] Failure Investigator (6h) failed #54072, [aw] Agent Job Health Monitor timed out #54094, [aw] No-Op Runs #48838, prior reports [aw-failures] [aw] Failure Investigator Report — 2026-08-19 07:05 UTC (6h) #53933/[aw-failures] [aw] Failure Investigator Report — 2026-08-16 13:00 UTC (6h) #53129/[aw-failures] [aw] Failure Investigator Report — 2026-08-13 19:10 UTC (6h) #52570/[aw-failures] [aw] Failure Investigator Report — 2026-08-13 (6h, updated 12:38 UTC) #52395) references this signature.
• No issues closed this cycle — no fresh evidence obtained that any of them are fixed or stale.

Fix roadmap

• P0 — do now: Rename or suffix the activation artifact so it passes GitHub's artifact-name validation (e.g. include run ID/job name in the name). Tracked in sub-issue below.
• P1 — none confirmed this cycle.
• P2 — monitor only: Watch for repeat Execute GitHub Copilot CLI / Execute Pi CLI exit-1 failures; open a tracked issue only once ≥2 runs share the same signature.

Sub-issues created

• P0 artifact-name-rejection fix (linked below).

References:

• https://github.com/github/gh-aw/actions/runs/32314806549
• https://github.com/github/gh-aw/actions/runs/32314804312
• https://github.com/github/gh-aw/actions/runs/32318213755

Generated by 🔍 [aw] Failure Investigator (6h) · agent · 83.4 AIC · ⌖ 8.84 AIC · ⊞ 5.9K · ◷

• expires on Aug 26, 2026, 5:20 PM UTC-08:00

[github-actions]

🍪 Issue Monster selected this for Copilot

I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.

If assignment succeeds, 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 · gpt54 · 2.99 AIC · ⌖ 7.88 AIC · ⊞ 12K · ◷