Rank, 14 days: 218 on the Claude Code sheet
3 people reported
All time, since Sep 22.
Invalid previous_message_id on resume
“On the next session start, Claude Code uses that UUID as previous_message_id, which the API rejects with a 400 error.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/claude-code/issues/2833/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Resumed session fails with 400 invalid previous_message_id. Next prompt after resume or session start is rejected because the stored anchor id lacks the msg_ prefix, such as a UUID or gateway id.
Is this your bug?
File my report- Where
- Session resume
- Error text
API Error: 400 diagnostics.previous_message_id: must be the `id` from a prior /v1/messages response (starts with `msg_`)Pasted in 2 reports- Versions
- 2.1.131
- Platforms
- macOS, Windows
- How bad
- Breaks a normal workflow.
Original reports3, newest first
claude --resumefails after mid-stream rate-limit: synthetic assistant entries poisonprevious_message_idchain#107331- 400 diagnostics.previous_message_id bricks a session after switching from an ANTHROPIC_BASE_URL gateway back to first-party (anchor accepts any requestId)#96916
- Session resume sends invalid previous_message_id (UUID) when prior session ended with connection error#96033