Skip to content

[aw-failures] Daily Sub-Agent Model Resolution Audit 100% red — Codex gpt-5-codex-alpha-2025-11-07 404s (same alpha-snapshot d [Content truncated due to length] #42033

Description

@github-actions

Apply the #41787 fix repo-wide — stop pinning the Codex alpha snapshot gpt-5-codex-alpha-2025-11-07. The same 404 defect tracked for Daily Cache Strategy Analyzer in #41787 also breaks this workflow, here 100% red for 5+ days.

Scope expansion of #41787 (not a duplicate). #41787 documents the alpha-snapshot 404 for a single workflow (Cache Strategy Analyzer, ~50% red). This issue records a second confirmed affected workflow with the identical signature and a worse cadence (every scheduled run since 6-24). Filing separately because the affected workflow and severity differ; fix should be cross-workflow.

Problem statement

The Execute Codex CLI step fails: every /responses sampling call returns 404 Not Found: Model not found gpt-5-codex-alpha-2025-11-07. The Codex harness retries 5× in-CLI, then classifies isInvalidModelError=true and does not retry the process (invalid/unsupported model configuration — not retrying). turns=0, 0 tokens, agent does zero useful work, job exits 1.

[codex-harness] awf-reflect: fetched 213 model(s) from (apiproxy/redacted)
[codex-harness] attempt 1: spawning: codex exec --model gpt-5.4-mini ...
{"type":"error","message":"unexpected status 404 Not Found: Model not found gpt-5-codex-alpha-2025-11-07, url: (172.30.0.30/redacted) ..."}
{"type":"turn.failed","error":{"message":"... Model not found gpt-5-codex-alpha-2025-11-07 ..."}}
[codex-harness] attempt 1 failed: ... isInvalidModelError=true ...
[codex-harness] attempt 1: invalid/unsupported model configuration — not retrying

Key detail: the harness top-level --model gpt-5.4-mini resolves fine (it is among the 213 models the proxy advertises). The 404 is on the actual /responses sampling call, which targets the pinned alpha snapshot gpt-5-codex-alpha-2025-11-07. So a sub-agent / Codex internal model config still pins the alpha snapshot even though the top-level agent model was migrated off it — directly relevant given this workflow audits sub-agent model resolution.

Affected workflow and run IDs

  • Workflow: Daily Sub-Agent Model Resolution Audit (.github/workflows/daily-model-resolution.lock.yml), engine codex.
  • Representative: §28314196736 — 2026-06-28, step Execute Codex CLI, 404 model-not-found, turns=0.
  • Recurrence (100% red, same step): §28281337868 (6-27), §28221799739 (6-26), §28151842380 (6-25), §28080204969 (6-24). Every scheduled run since 6-24 failed.
  • Firewall is clean (15/15 requests allowed, 0 blocked) — this is purely model availability, not network/firewall.

Probable root cause

Identical to #41787: a preview/alpha Codex snapshot (gpt-5-codex-alpha-2025-11-07) that the AIC api-proxy (172.30.0.30:10000) does not serve. Here the snapshot is pinned for a sub-agent / Codex sampling config rather than the top-level agent model, so migrating the agent model alone did not fix it. There is no degraded mode — every sampling call 404s and the run is a total loss.

Proposed remediation

  1. Sweep all Codex-engine workflows and sub-agent model configs for the pinned alpha snapshot gpt-5-codex-alpha-2025-11-07; repoint to a stable/GA Codex model (or add a fallback). This generalizes [aw-failures] Daily Cache Strategy Analyzer ~50% red — Codex pinned to alpha snapshot gpt-5-codex-alpha-2025-11-07 that 404s on [Content truncated due to length] #41787 beyond Cache Strategy Analyzer.
  2. Make the Codex harness fail fast on 404 model not found (already non-retried, but it still burns 5 in-CLI sampling retries first) and surface the offending model name in the job summary.
  3. Add a compile-time / preflight check that rejects known-unavailable alpha snapshots in workflow + sub-agent frontmatter so this cannot reach CI.

Success criteria / verification

  1. A subsequent scheduled Daily Sub-Agent Model Resolution Audit run reaches turns>0 and completes without a 404.
  2. No Codex-engine workflow or sub-agent config references gpt-5-codex-alpha-2025-11-07.
  3. [aw-failures] Daily Cache Strategy Analyzer ~50% red — Codex pinned to alpha snapshot gpt-5-codex-alpha-2025-11-07 that 404s on [Content truncated due to length] #41787 and this issue can both close once the alpha-snapshot pin is removed repo-wide.

Generated by 🔍 [aw] Failure Investigator (6h) · 280.5 AIC · ⌖ 35.7 AIC · ⊞ 5.2K ·

  • expires on Jul 5, 2026, 12:15 AM UTC-08:00

Metadata

Metadata

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions