claude-code - 💡(How to fix) Fix [Bug] Tool result submission returns 404 Not Found error [5 comments, 4 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#51903Fetched 2026-04-23 07:41:50
View on GitHub
Comments
5
Participants
4
Timeline
12
Reactions
3
Author
Timeline (top)
commented ×5cross-referenced ×3subscribed ×2labeled ×1

Code Example

[]
RAW_BUFFERClick to expand / collapse

Bug Description Hello,

I have a persistent Claude tools issue.

Any tool invocation eventually fails with: “Tool result could not be submitted. The request may have expired or the connection was interrupted.”

In DevTools I consistently see: POST /api/organizations/.../chat_conversations/.../tool_result404 Not Found

At the same time, normal completions succeed: [COMPLETION] Completion request succeeded on attempt 1

This reproduces across new chats and persists in both Claude Web and Claude Desktop.

The tools themselves appear to execute, but Claude fails when submitting the final tool result back into the conversation.

Please check whether tool-result routing or session state is broken for my account/workspace.

Thank you.

Environment Info

  • Platform: darwin
  • Terminal: Apple_Terminal
  • Version: 2.1.116
  • Feedback ID: e79f00cc-ed1e-487d-a1e9-8e52d7197f8a

Errors

[]

extent analysis

TL;DR

The issue is likely due to a routing or session state problem with tool result submissions, and checking the tool-result routing or session state for the account/workspace may resolve the issue.

Guidance

  • Investigate the POST /api/organizations/.../chat_conversations/.../tool_result endpoint to determine why it's returning a 404 Not Found error, as this is the point of failure.
  • Verify that the tool result submission is correctly formatted and that the conversation ID and organization ID are valid.
  • Check the session state to ensure it's not expiring or being interrupted, causing the tool result submission to fail.
  • Compare the successful completion requests ([COMPLETION] Completion request succeeded on attempt 1) to the failed tool result submissions to identify any differences in the request or response.

Example

No code snippet is provided as the issue doesn't contain specific code-related details.

Notes

The issue seems to be specific to the tool result submission process, and the successful completion requests suggest that the issue is not with the tool execution itself. The 404 Not Found error indicates a potential routing or endpoint issue.

Recommendation

Apply workaround: Investigate and potentially modify the tool-result routing or session state configuration to resolve the issue, as the problem seems to be specific to the account/workspace configuration.

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

claude-code - 💡(How to fix) Fix [Bug] Tool result submission returns 404 Not Found error [5 comments, 4 participants]