[workflow-analysis] Weekly Workflow Analysis — 2026-03-17 to 2026-03-23 #22403
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it expired on 2026-03-24T09:44:42.637Z.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
This report covers agentic workflow runs from the past week (2026-03-16 → 2026-03-23) across Claude and Codex engines.
Summary
Failure Analysis
Schema Feature Coverage Checker — §23425050593
failure(insafe_outputsjob)make recompile/make agent-finish) callsgo mod download, which attempts to reachproxy.golang.org. This domain is blocked by the network firewall (243 of 269 requests blocked).bots,command,container,disable-model-invocation,environment,github-app,infer,labels,metadata,post-steps). However, the PR could not be submitted because safe-output validation failed.private,run-name,secretsFirewall breakdown for Schema Feature Coverage Checker
api.openai.com:443proxy.golang.org:443ab.chatgpt.com:443Recommendation: Add
proxy.golang.orgto the allowed network domains for the Schema Feature Coverage Checker workflow, or restructure validation to avoid requiringgo mod downloadat agent runtime.DIFC Integrity Filtering
The DIFC integrity gateway filtered several resources across both engines. These are security controls working as intended — agents cannot read content from untrusted contributors unless it meets integrity thresholds.
Filtered events this week
search_pull_requestssearch_pull_requestssearch_issuessearch_issuessearch_issuesissue_readNotable: The AI Moderator was unable to read issue #22380 (integrity below threshold), causing a
missing_datasignal. The moderator correctly reported this limitation rather than silently failing.Performance Metrics (Claude Engine)
Per-run breakdown
Observation: The Daily Documentation Updater consumed 3.6M tokens across 52 turns (~$1.77). This is a notably high token count for a documentation task. The agent made 6
pull_request_readcalls and 2search_issuescalls, suggesting it may be doing broad PR/issue scanning that could be scoped more narrowly.Recommendation: Consider adding explicit scope filters to the Daily Documentation Updater (e.g., filter by date range, label, or specific sections) to reduce context size and cost.
Firewall Analysis — Codex Engine
The Codex firewall blocked
ab.chatgpt.comconsistently across all runs (3–4 blocked requests per run). This is expected behavior — it's OpenAI telemetry/analytics traffic and does not affect workflow outcomes.The only actionable firewall issue is
proxy.golang.orgfor the Schema Feature Coverage Checker (see failure analysis above).Reliability Metrics by Workflow
proxy.golang.orgRecommendations Summary
proxy.golang.orgto allowed network domainsReferences:
Beta Was this translation helpful? Give feedback.
All reactions