Repository navigation
[aw] Workflow Normalizer could not verify daily AI credits #61139
Description
Workflow Failure
Workflow: Workflow Normalizer
Branch: main
Run: https://github.com/github/gh-aw/actions/runs/34971314193
Warning
Daily Workflow AI Credits Could Not Be Verified: The agent was not started because the daily guardrail could not prove complete AI Credits accounting for earlier workflow runs.
Guardrail status: transient_error
Reason: Daily workflow AI Credits are unknown: Missing accounting for executed agent component in run 34845857175 (attempt 1, job 103981961916, conclusion cancelled): agent/token_usage.jsonl is missing; agent_usage.jsonl is missing; agent_usage.json is missing
The guardrail fails closed either because a billable component's usage artifact is missing, empty, or unreadable, or because the guardrail could not reach the GitHub API to verify prior runs. The detailed reason above identifies the specific cause.
This means a billable component in a prior run completed without leaving a valid accounting record. Inspect the affected prior run and its component logs. Once that run leaves the rolling 24-hour window, the guardrail can evaluate the remaining runs normally.
Action Required
Assign this issue to an agent to debug and fix the issue.
Debug with any coding agent
Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):
Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md
The failed workflow run is at https://github.com/github/gh-aw/actions/runs/34971314193
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.
- Start your agent
- Load the
agentic-workflowsskill from.github/skills/agentic-workflows/SKILL.mdor https://github.com/github/gh-aw/blob/main/.github/skills/agentic-workflows/SKILL.md - Type
debug the agentic workflow workflow-normalizer failure in https://github.com/github/gh-aw/actions/runs/34971314193
Tip
Stop reporting this workflow as a failure
To stop a workflow from creating failure issues, set report-failure-as-issue: false in its frontmatter:
safe-outputs:
report-failure-as-issue: falseGenerated from Workflow Normalizer · ◷
- expires on Sep 16, 2026, 12:53 AM UTC
Activity
github-actions commentedon Sep 16, 2026
This issue was automatically closed because it expired on 2026-09-16T00:53:34.234Z.