githubnext / githubnext/gh-aw-cao

[aw] SelfCare hit HTTP 400 bad request

Closed
#11,797 56 comments 0 reactions 0 assignees View on GitHub
agentic-workflows
Dominant language
JavaScript
Stars
3
Forks
1
Avg merge
49m
Merged PRs (30d)
837

Description

### Workflow Failure

**Workflow:** [SelfCare](#)
**Branch:** main
**Run:** https://github.com/githubnext/gh-aw-cao/actions/runs/35019200904

> [!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

1. Inspect the run's `agent-stdio.log` and `safeoutputs.jsonl` artifacts around the first HTTP 400.
2. Check for malformed request data, invalid tool-call payloads, or stale conversation state being replayed.
3. 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:**
```
400 Bad Request
Changes +0 -0
Duration 0s
Resume copilot --resume=3fbbe17e-3198-4828-af24-91c8b4d658af
```

### 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/githubnext/gh-aw-cao/actions/runs/35019200904
````

Manually invoke the agent

Debug this workflow failure using your favorite Agent CLI and the `agentic-workflows` prompt.

- Start your agent
- Load the `agentic-workflows` skill from `.github/skills/agentic-workflows/SKILL.md` or
- Type `debug the agentic workflow self-care failure in https://github.com/githubnext/gh-aw-cao/actions/runs/35019200904`

> [!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:
> ```yaml
> safe-outputs:
> report-failure-as-issue: false
> ```
>
>

> Generated from [SelfCare](https://github.com/githubnext/gh-aw-cao/actions/runs/35019200904) · [◷](https://github.com/search?q=repo%3Agithubnext%2Fgh-aw-cao+is%3Aissue+%22gh-aw-workflow-id%3A+self-care%22&type=issues)
> - [x] expires on Sep 16, 2026, 8:26 PM UTC

Contributor guide

Open the contributing guide

Research direction

Start with debug.md and the failed workflow run, then inspect the agent-stdio.log and safeoutputs.jsonl artifacts around the first HTTP 400. Compare resumed and fresh runs as suggested; done means identifying the request or persisted-state cause and confirming the SelfCare workflow completes without the engine failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.