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
Prefer ET budget controls for diagnosis instead of run-count heuristics. You can tune this limit with max-effective-tokens in workflow frontmatter.
Action Required
Assign this issue to Copilot using the agentic-workflows sub-agent to automatically debug and fix the workflow failure.
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/25879488585
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.
Workflow Failure
Workflow: Daily Cache Strategy Analyzer
Branch: main
Run: https://github.com/github/gh-aw/actions/runs/25879488585
⛔ Effective Token Budget Exhausted: The run failed due to effective-token budget/rate-limit enforcement in the API proxy.
25MPrefer ET budget controls for diagnosis instead of run-count heuristics. You can tune this limit with
max-effective-tokensin workflow frontmatter.Action Required
Assign this issue to Copilot using the
agentic-workflowssub-agent to automatically debug and fix the workflow failure.Debug with any coding agent
Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the
agentic-workflowsprompt.agentic-workflowsprompt from.github/agents/agentic-workflows.agent.mdor https://github.com/github/gh-aw/blob/main/.github/agents/agentic-workflows.agent.mddebug the agentic workflow daily-cache-strategy-analyzer failure in https://github.com/github/gh-aw/actions/runs/25879488585Tip
Stop reporting this workflow as a failure
To stop a workflow from creating failure issues, set
report-failure-as-issue: falsein its frontmatter: