You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The audit command comparison delta always shows turns.after = 0 regardless of the actual number of turns the workflow run executed. This causes all runs to appear as regressions (turns_decrease) compared to their baselines even when the run completed successfully with many turns.
All three audited runs show after: 0, triggering false turns_decrease regression classification.
Root Cause Hypothesis
The token_usage.jsonl file is empty (0 bytes) for all recent runs. The audit comparison logic likely reads per-turn counts from this file. Since it is empty, turns always computes to 0. For comparison:
token_usage.jsonl: 0 lines for all tested runs
agent_usage.json: correct totals (input_tokens, output_tokens, cache data present)
metrics.turns: correctly populated for claude runs (e.g., 34 for run 28731332447)
Impact
Severity: Medium
Frequency: Always (100% of audited runs across claude, copilot, and codex engines)
Workaround: Use metrics.turns directly; ignore comparison.delta.turns.after
Affected Runs Tested
Run ID
Workflow
Engine
metrics.turns
delta.after
28731332447
Static Analysis Report
claude
34
0
28731939775
Duplicate Code Detector
codex
None
0
28731355046
Daily Windows Terminal
copilot
None
0
Environment
Repository: github/gh-aw
Run ID: 28731918594
Date: 2026-07-05
AWF version: v0.27.22 (agent version 1.0.68)
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
awmgmcpg
To allow these domains, add them to the network.allowed list in your workflow frontmatter:
Problem Description
The
auditcommand comparison delta always showsturns.after = 0regardless of the actual number of turns the workflow run executed. This causes all runs to appear as regressions (turns_decrease) compared to their baselines even when the run completed successfully with many turns.Command/Tool
auditagenticworkflows audit --run_id <run_id>Steps to Reproduce
agenticworkflows audit --run_id 28731332447 --max_tokens 3000comparison.delta.turnsmetrics.turnsExpected Behavior
comparison.delta.turns.aftershould equal the actual turn count frommetrics.turnsfor the current run.Actual Behavior
comparison.delta.turns.afteralways shows0even whenmetrics.turnsshows the real count:All three audited runs show
after: 0, triggering falseturns_decreaseregression classification.Root Cause Hypothesis
The
token_usage.jsonlfile is empty (0 bytes) for all recent runs. The audit comparison logic likely reads per-turn counts from this file. Since it is empty, turns always computes to 0. For comparison:token_usage.jsonl: 0 lines for all tested runsagent_usage.json: correct totals (input_tokens, output_tokens, cache data present)metrics.turns: correctly populated for claude runs (e.g., 34 for run 28731332447)Impact
metrics.turnsdirectly; ignorecomparison.delta.turns.afterAffected Runs Tested
Environment
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
awmgmcpgSee Network Configuration for more information.