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
🚦 Engine Rate Limited (HTTP 429): The copilot engine hit provider rate limits and could not complete this run.
This signal was detected from engine runtime logs/OTLP telemetry.
What to do next
Retry the workflow after a short delay.
If this keeps happening, reduce concurrent workflow volume or review provider quota/rate-limit policies.
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/26681099411
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.
Workflow Failure
Workflow: Package Specification Extractor
Branch: main
Run: https://github.com/github/gh-aw/actions/runs/26681099411
🚦 Engine Rate Limited (HTTP 429): The
copilotengine hit provider rate limits and could not complete this run.This signal was detected from engine runtime logs/OTLP telemetry.
What to do next
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.):
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the
agentic-workflowsprompt.agentic-workflowsskill from.github/skills/agentic-workflows/SKILL.mdor https://github.com/github/gh-aw/blob/main/.github/skills/agentic-workflows/SKILL.mddebug the agentic workflow spec-extractor failure in https://github.com/github/gh-aw/actions/runs/26681099411Tip
Stop reporting this workflow as a failure
To stop a workflow from creating failure issues, set
report-failure-as-issue: falsein its frontmatter: