Draft
No code fix: Daily Evals Feature Report failure is an external credential issue, not a repo defect#55040
Conversation
Copilot
AI
changed the title
[WIP] Fix daily evals feature report workflow failure
No code fix: Daily Evals Feature Report failure is an external credential issue, not a repo defect
Aug 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Investigated the
Daily Evals Feature Reportworkflow failure (401 Unauthorized from OpenAI via thecodexengine). No code changes were made, since the root cause is outside this repository's control.Findings
awffirewall/proxy sidecar (ghcr.io/github/gh-aw-firewall/api-proxy) — not from any compiler or workflow logic in this repo.actions/setup/sh/validate_multi_secret.sh) andCODEX_API_KEY/OPENAI_API_KEYfallback are already in place. Requests are correctly routed through the gateway, unlike the historical stale-lock-file incidents ([aw-failures] 6h Failure Report 2026-04-22: Codex 401 Auth Loop — Lock File Root Cause Identified #27729/[aw-failures] Recompile lock files to fix Codex 401 Unauthorized failures (blocks AI Moderator + Daily Obs Report) #27731) where requests bypassed the proxy entirely.OPENAI_API_KEY/CODEX_API_KEYsecret itself being invalid or expired — a credential-rotation issue, matching the pattern of previously-closed incidents ([aw-failures] Codex engine 401 auth failure — OPENAI_API_KEY credential missing or invalid #27127, [aw-failures] AI Moderator — codex engine persistent 401 auth failure (OPENAI_API_KEY invalid or expired) #26929, [aw-failures] Fix AI Moderator OpenAI API credentials — 401 Unauthorized (Codex engine, 100% failure rate) #27654) resolved without code changes.Why no code change
Modifying
daily-evals-report.md(e.g. switching engines) would mask the symptom for a single workflow while every other Codex-engine workflow in the repo remains broken, and would need to be reverted once the credential is rotated.Next step
Rotate/verify the
OPENAI_API_KEY/CODEX_API_KEYsecret at the repository or org level; no further workflow-definition changes are needed once the credential is valid.