Overview
Period: 2026-09-12 12:42 UTC to 2026-09-13 01:12 UTC
Runs analyzed: 3 (0 had token data)
Total tokens: 0 across all workflows (no token_usage data reported)
Estimated total cost: $0.00 (no estimated_cost data reported)
Total Actions minutes: 16 min
Only one Claude-engine workflow ran in this period: Smoke Claude. All 3 runs completed successfully with no reported errors or warnings. However, token_usage, estimated_cost, turns, error_count, warning_count, and token_usage_summary were all null for every run — no cost/token instrumentation data was available this cycle, so no optimization analysis could be performed against the defined thresholds.
Workflow Summary
| Workflow |
Runs |
Total Tokens |
Avg Tokens |
Cost |
Avg Cost |
Turns |
| Smoke Claude |
3 |
N/A |
N/A |
N/A |
N/A |
N/A |
🔍 Optimization Opportunities
No optimization analysis could be performed — all token/cost/turn fields were null for every run in this period. This differs from the prior report where token_usage and estimated_cost were populated (just missing turns/token_usage_summary).
- Action needed: Verify the api-proxy sidecar is running and emitting usage data for the
smoke-claude workflow. If --enable-api-proxy was disabled, or the sidecar failed health checks, no token accounting will be captured at all.
- Action minutes (16 total, ~5.3/run) are consistent with the historical baseline (~5.75/run), so runtime behavior itself appears unchanged — this looks like a data-instrumentation regression rather than a workload change.
Per-Workflow Details
Smoke Claude (.github/workflows/smoke-claude.lock.yml)
- Runs: 3 — §34729955616, §34722434907, §34694400539
- Total tokens: N/A (
token_usage null for all runs)
- Estimated cost: N/A (
estimated_cost null for all runs)
- Action minutes: 16 total (avg 5.3/run) — durations: 4.2m, 5.1m, 4.7m
- Turns: not available (
turns null for all runs)
- Model/cache breakdown: not available (
token_usage_summary null for all runs)
- Error rate: 0/3 runs (conclusion: success for all)
Workflows Without Token Data
All 3 runs in this period (all "Smoke Claude") had token_usage null/missing:
This suggests the api-proxy token-tracking instrumentation is not currently emitting data for this workflow, worth investigating.
Historical Trend
Found 5 previous Claude token usage report issues (#8484, #8446, #8381, #8347, #8313). The most recent (#8484, covering 2026-09-11 → 2026-09-12) reported 4 runs of Smoke Claude with 20K total tokens (avg 5.0K/run) and 214.35 total AI credits — i.e., token/cost data was available then. In this period all such fields are null, indicating a likely regression in token-usage instrumentation (e.g., api-proxy sidecar not reporting) rather than an actual change in workflow cost or behavior, since Actions-minute durations remain in the same range (~5min/run) as before.
Previous Report
#8484
Generated by Daily Claude Token Usage Analyzer · copilot · auto · 31.6 AIC · ⊞ 11.9K · ◷
Overview
Period: 2026-09-12 12:42 UTC to 2026-09-13 01:12 UTC
Runs analyzed: 3 (0 had token data)
Total tokens: 0 across all workflows (no
token_usagedata reported)Estimated total cost: $0.00 (no
estimated_costdata reported)Total Actions minutes: 16 min
Only one Claude-engine workflow ran in this period: Smoke Claude. All 3 runs completed successfully with no reported errors or warnings. However,
token_usage,estimated_cost,turns,error_count,warning_count, andtoken_usage_summarywere allnullfor every run — no cost/token instrumentation data was available this cycle, so no optimization analysis could be performed against the defined thresholds.Workflow Summary
🔍 Optimization Opportunities
No optimization analysis could be performed — all token/cost/turn fields were
nullfor every run in this period. This differs from the prior report wheretoken_usageandestimated_costwere populated (just missingturns/token_usage_summary).smoke-claudeworkflow. If--enable-api-proxywas disabled, or the sidecar failed health checks, no token accounting will be captured at all.Per-Workflow Details
Smoke Claude (
.github/workflows/smoke-claude.lock.yml)token_usagenull for all runs)estimated_costnull for all runs)turnsnull for all runs)token_usage_summarynull for all runs)Workflows Without Token Data
All 3 runs in this period (all "Smoke Claude") had
token_usagenull/missing:This suggests the api-proxy token-tracking instrumentation is not currently emitting data for this workflow, worth investigating.
Historical Trend
Found 5 previous Claude token usage report issues (#8484, #8446, #8381, #8347, #8313). The most recent (#8484, covering 2026-09-11 → 2026-09-12) reported 4 runs of Smoke Claude with 20K total tokens (avg 5.0K/run) and 214.35 total AI credits — i.e., token/cost data was available then. In this period all such fields are
null, indicating a likely regression in token-usage instrumentation (e.g., api-proxy sidecar not reporting) rather than an actual change in workflow cost or behavior, since Actions-minute durations remain in the same range (~5min/run) as before.Previous Report
#8484