published Aug 25, 2026, 6:03 AM · updated Aug 25, 2026, 6:45 AM
Workflow Failure
Workflow: Daily VulnHunter Scan
Branch: main
Run: https://github.com/github/gh-aw/actions/runs/32814355410
Warning
Engine Max Runs Exceeded: The claude engine hit the workflow max runs guardrail and could not continue.
This signal was detected from engine runtime logs.
What to do next
- Increase workflow
max-runsif the task legitimately needs more model invocations. - Reduce per-run model calls by simplifying prompts, limiting retries, or breaking work into smaller steps.
- Review the run logs to identify repeated loops or retries that consumed invocation budget unexpectedly.
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/32814355410
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 daily-vulnhunter-scan failure in https://github.com/github/gh-aw/actions/runs/32814355410
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 Daily VulnHunter Scan · claude · 747.7 AIC · ◷
- expires on Aug 25, 2026, 6:03 PM UTC