Repository navigation
[aw] Duplicate Code Detector hit HTTP 400 bad request #8600
Description
Workflow Failure
Workflow: Duplicate Code Detector
Branch: main
Run: https://github.com/github/gh-aw-firewall/actions/runs/35026797094
Warning
HTTP 400 Bad Request from agentic engine: The agent failed after the engine returned Response status code does not indicate success: 400 (Bad Request).
This is usually a request validation failure rather than a timeout or quota issue.
How to debug this
- Inspect the run's
agent-stdio.logandsafeoutputs.jsonlartifacts around the first HTTP 400. - Check for malformed request data, invalid tool-call payloads, or stale conversation state being replayed.
- If the failure happened on a resumed session, rerun fresh once to confirm whether persisted state is corrupt.
Warning
Engine Failure: The copilot engine terminated unexpectedly.
Last agent output:
#49 [agent] resolving provenance for metadata file
#49 DONE 0.0s
agent Built
api-proxy Built
400 Bad Request
Changes +0 -0
Duration 0s
Resume copilot --resume=d0b57992-7e9c-4374-8888-19949a0449c7
Run 'docker run --help' for more information
Run 'docker run --help' for more information
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-firewall/actions/runs/35026797094
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 duplicate-code-detector failure in https://github.com/github/gh-aw-firewall/actions/runs/35026797094
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 Duplicate Code Detector · ◷
- expires on Sep 22, 2026, 9:42 PM UTC
Activity