claude-code - 💡(How to fix) Fix Recurring "No message found with message.uuid" error when continuing a chat [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#56024Fetched 2026-05-05 06:00:09
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×3commented ×1

Error Message

Working in a Claude Code chat earlier today (2026-05-04), the session repeatedly returned this error and could not be continued:

Claude Code returned an error result: No message found with message.uuid of: <uuid>

  1. The session reports the error above before%2
RAW_BUFFERClick to expand / collapse

What happened

Working in a Claude Code chat earlier today (2026-05-04), the session repeatedly returned this error and could not be continued:

Claude Code returned an error result: No message found with message.uuid of: <uuid>

It has happened multiple times in the same day with different UUIDs each time — so it is not a single corrupted message, the bug is recurring. Observed UUIDs so far:

  • cb5f226a-8143-4fc8-8a04-e0c17240ae4a
  • 0faffae0-bd0d-4321-9eeb-05c909705564

The chat had been actively in use the same day before the errors started — it was not a long-dormant session.

Steps to reproduce

  1. Open Claude Code and work in a chat for a while (the affected chat had real activity earlier today).
  2. Continue or resume the same chat (e.g. claude --resume or the resume picker).
  3. The session reports the error above before%2

extent analysis

TL;DR

The issue may be related to message synchronization or storage, and verifying message integrity or retrying the session could help resolve the error.

Guidance

  • Check if the error occurs consistently with the same chat session or if it's intermittent across different sessions.
  • Verify if the issue is specific to the claude --resume command or if it also happens when resuming through the picker.
  • Investigate if there are any patterns or correlations between the error occurrences, such as time of day or specific actions taken in the chat.
  • Consider retrying the session or attempting to recover the lost messages to see if the issue resolves itself.

Notes

The provided information suggests a potential issue with message storage or synchronization, but more details are needed to determine the root cause. The fact that different UUIDs are affected each time suggests that it's not a single corrupted message.

Recommendation

Apply workaround: Retry the session or attempt to recover the lost messages, as this may help resolve the error and provide more insight into the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING