[BUG] [Error] Tool result could not be submitted.

I can confirm this issue and it appears to be the same underlying bug.

In my case:

• normal completions still succeed
• tool-assisted turns fail at the final handoff step
• POST /api/organizations/.../chat_conversations/.../tool_result returns 404 Not Found
• the UI shows: Tool result could not be submitted. The request may have expired or the connection was interrupted.
• tools may appear to execute, including file creation/modification, but the final tool result cannot be submitted back into the conversation

Reproduced across new chats, and in both Claude Web and Claude Desktop on macOS.

This looks like a broken tool-result submission/session-state issue rather than a generic connectivity problem.

I am also experiencing this issue, as of upgrading to Claude 1.3883.0 (93ff6c) 2026-04-21T17:24:01.000Z today. I did not experience this issue on previous versions.

Every tool call is generating this error, on both Claude Desktop and Claude Web chat.

this is also happening to me when trying to call on custom skills that I made. This did not happen when I first uploaded/created the skills and it happens with every call.

Same problem when I updating to the latest version. I assume that the Opus 4.7 need calling sub-agent or something, and then Claude forgot it runs on Desktop rather than Website. Then print this warning. LOL

It's not an Opus 4.7 issue as I am running into it on Sonnet 4.5 as well.

Same issue here. Only started today.

Same issue - started about an hour ago ~12pm UTC. Sonnet 4.6 on web. Any time there's an uploaded file the issue appears.

Same issue with Sonnet 4.6. Again, started today (22/04/2026)

Same. With a personal skill.

Every single day a new issue pops up.. why am I even still here.. get it together Anthropic!!

Same this started happening after the latest update. Nothing else had changed on my part.

Same here after the last update. Claude Desktop app on W11 (Claude 1.3883.0 (93ff6c) 2026-04-21T17:24:01.000Z) using Sonnet 4.6
Edit: The session limit also seems to be reached much earlier.

Also just updated and experiencing same issue. MacOS Claude 1.3883.0 (93ff6c) 2026-04-21T17:24:01.000Z using all models.

Super annoying. Happens pretty much every single time Claude does anything (read, write an MD, web search, lookign for a file..).
Claude 1.3883.0 (93ff6c) 2026-04-21T17:24:01.000Z. (Claude Desktop for Mac)
All models impacted.
Seems to consume usage faster too.

Exact same thing happens to me. with leak of the token usage also. that's crazy. I've heard that could make the quality of answer itself much worse because the tools and thinking logic cannot be verified by server.

Using MacOS Claude 1.3883.0 (93ff6c) also.

I get the same message I am using Firefox 149.02 Mozilla FireFox Snap for Ubuntu, Zorin OS (Ubuntu 24.04) I am using the FireFox sidebar tool with Claude Sonnet 4.6 Adaptive

Same issue here

I am also seeing the same issue. Occurs on both MacOS Claude 1.3883.0 (93ff6c) 2026-04-21T17:24:01.000Z and Claude.ai

Same issue as of today. No change to my setup other than the latest update. Error appears even when there is no visible failure in performance

I'm seeing this with a gentoo linux and fresh firefox emerge today.

same issue here

https://isdown.app/status/claude-ai/ has quite a few with the same issue, too.
Tried web, desktop, deactivated all MCP: no luck.

I can report the same issue. Mine has been happening since yesterday. Tried all suggested solutions. Using Windows Claude Desktop.
Build: Claude Desktop 1.3883.0.0 (MSIX, Windows)
Issue: Every tool call (including built-in web_search, no MCP involved) results in repeated HTTP 404 on POST /api/organizations/.../chat_conversations/{id}/tool_result. The retry loop continues indefinitely with exponential backoff, firing toast errors for the entire session. Persists across full app restarts, machine reboots, and new conversations. The conversation ID changes per session but the 404 behavior is consistent.
Log source: %APPDATA%\Claude\logs\claude.ai-web.log
Example error: not_found_error / statusCode: 404 on endpoint .../chat_conversations/3c381c70-3d8d-4eeb-9880-5509e916fc0e/tool_result
Impact: Cosmetic only — chats complete successfully — but the retry loop generates continuous noise and may indicate tool results are not actually being persisted server-side.

I'm seeing the same issue. Claude Desktop for Mac, version 1.3883.0 (93ff6c) 2026-04-21T17:24:01.000Z.

It's trying to create files (markdown) and fails. For one chat, it failed completely and lost the work that it was doing.

Same here. Started yesterday.
If of any use, the following is a report that claude made as this error showed up many times when I handed it the console log.

[BUG] POST /tool_result returns HTTP 404, surfaced to user as "request may have expired or the connection was interrupted"

Summary

On claude.ai (web), every tool call in an active conversation fails with the UI banner:

Tool result could not be submitted. The request may have expired or the connection was interrupted. Refresh the page to continue.

Firefox console + network logs show this is not a timeout or dropped connection. The client's POST to /api/organizations/{org}/chat_conversations/{conv}/tool_result returns HTTP 404 in 300–470 ms — a fast, deliberate "not found" from the server. Retries produce the same 404. The user-facing message is misleading about the underlying cause.

This appears related to or a duplicate of #51874, but with a concrete server-side failure mode (404 on /tool_result) that wasn't captured in that report.

Environment

• Product: claude.ai (web), not the desktop app
• Browser: Firefox
• Client asset bundle: index-C9LNZ2RA.js
• Date observed: 2026-04-22

Reproduction

1. Open a conversation on claude.ai in Firefox.
2. Send a prompt that causes the assistant to invoke any tool (web search, file creation, artifact rendering, etc.).
3. The tool call itself appears to execute, but the client then fails to submit the result.
4. The red banner appears inline. Retries fail identically. New messages in the same conversation that trigger tool calls also fail.

Observed across multiple different tools in the same session, which rules out a single tool being at fault.

Observed behaviour — network layer

Five consecutive POSTs to the tool-result endpoint, all returning 404:

XHR POST https://claude.ai/api/organizations/{org}/chat_conversations/{conv}/tool_result
[HTTP/3 404  372ms]
[HTTP/3 404  376ms]
[HTTP/3 404  300ms]
[HTTP/3 404  311ms]
[HTTP/3 404  469ms]

Status          404
Version         HTTP/3
Transferred     783 B (282 B size)
Referrer Policy strict-origin-when-cross-origin

Response sizes (~282 B) are consistent with a structured JSON error body, not an HTML error page or a proxy timeout.

Near the end of the session, a separate artifact lookup also 404s — possibly a downstream consequence of the same out-of-sync state:

XHR GET https://claude.ai/api/organizations/{org}/artifacts/wiggle_artifact/{artifact_id}/tools
  ?chat_conversation_uuid={conv}&file_path=/outputs/claude-tool-error-report.docx
[HTTP/3 404  469ms]

[REACT_QUERY_CLIENT] QueryClient error: Error: Artifact not found

Observed behaviour — client layer

Each 404 is caught by the React Query mutation handler and re-thrown as the generic "expired / interrupted" error, which is what the UI displays:

[REACT_QUERY_CLIENT] QueryClient error: Error: Tool result could not be submitted.
The request may have expired or the connection was interrupted. Refresh the page to continue.
    ib https://assets-proxy.anthropic.com/claude-ai/v2/assets/v1/index-C9LNZ2RA.js:2
    ob https://assets-proxy.anthropic.com/claude-ai/v2/assets/v1/index-C9LNZ2RA.js:2
    dM https://assets-proxy.anthropic.com/claude-ai/v2/assets/v1/index-C9LNZ2RA.js:3
    mutationFn https://assets-proxy.anthropic.com/claude-ai/v2/assets/v1/index-C9LNZ2RA.js:3

Uncaught (in promise) Error: Tool result could not be submitted. ...

Note that subsequent [COMPLETION] log lines still report Completion request succeeded on attempt 1 — so completion calls continue to work, only the tool-result POST is broken.

Analysis

POST /chat_conversations/{conv}/tool_result expects a pending tool call on the specified conversation that's waiting for a result. A 404 on this endpoint means one of:

• the conversation record can't be located for the {org}/{conv} pair, or
• there's no pending tool call matching the tool_use_id the client is submitting a result for.

Given that completion requests on the same conversation continue to succeed, the conversation itself exists. The most likely cause is that the tool_use / tool_result records are out of sync between client and server — the client believes there's an outstanding tool call to answer, but the server has no matching pending call to accept the result into.

A page refresh will not fix this, because the server genuinely doesn't have a slot for the result the browser is trying to post. This matches user reports in #51874 that the error persists across refreshes and new chats.

Expected behaviour

Either:

1. The server accepts the tool_result POST because the pending tool call still exists, and the conversation continues, or
2. If the server has legitimately lost the pending-tool-call state, the client surfaces a specific, accurate error ("the pending tool call is no longer available on the server, the turn cannot be completed") rather than a misleading "request may have expired or the connection was interrupted" message that points users toward network/transport fixes that don't apply.

Additional notes

• The UI message should probably be differentiated by underlying cause. A 404 from the server is a very different signal from an actual timeout or network drop, and conflating them sends users down the wrong debugging path (checking their network, disabling connectors, restarting the app) when the fault is server-side state.
• Related/possibly-duplicate: #51874 (same user-facing message; this report adds the HTTP-layer detail).
• Related by pattern: #51128, #15137 (tool_result content processing and post-auth-retry failures).

Hi,
I ran into this problem too.
I have 2 machines running Claude Desktop (Windows) :

Claude 1.3883.0 (93ff6c) 2026-04-21 — has the tool result error
Claude 1.3109.0 (35cbf6) 2026-04-16 — no error at all

The older version seems to work fine, so if anyone needs to revert:
https://claude.en.uptodown.com/windows/versions
https://claude.en.uptodown.com/mac/versions
Hope it helps!

"Tool result could not be submitted. The request may have expired or the connection was interrupted. Refresh the page to continue. - Error Message"

Having the same issue, even in new chats, anything that calls for web usage. This is from the error log:

Title: Tool result could not be submitted — 404 on /tool_result endpoint for all tool calls
Description:
Any tool invocation (web search, image search, MCP connectors) returns a 404 error immediately. Happens in brand new chats with no context. The error appears in claude.ai-web.log:
[REACT_QUERY_CLIENT] QueryClient error: 404
endpoint: /api/organizations/<org_id>/chat_conversations/<id>/tool_result
method: POST
message: "Tool result could not be submitted. The request may have expired
or the connection was interrupted."
errorCode: not_found_error
Environment: macOS, Claude Desktop app, Max plan
Reproducible: 100%, every tool call, every new conversation
Workaround: None. Tool calls complete on backend (response is returned) but client cannot submit the result back.

Same is happening for me. Seems like it possibly started after I upgraded on MacOS to the latest version but I saw it at least once on the browser version, too. Also seems like I'm getting an usually high level of "Claude reached its tool-use limit for this turn." and have reached my session limit more quickly and am now paying for overages.

Same issue... it's happening on the Mac OS M4 Pro. Driving me nuts tbh

I've tried Claude Ai and Claude Code (cloud) in the web browser, and exact same error.

Does anyone know why this was tagged "invalid" ? It's a perfectly valid issue that does impact Claude Code alongside Claude Chat!

Same issue here, started yesterday (Apr 21, 2026).

Environment

• Claude Desktop on Windows
• Also reproduces on claude.ai web (same account, different session)
• Multiple MCP connectors active: n8n, custom VPS dev server, GitHub MCP,

Gmail, Google Calendar, Google Drive

• Location: Mexico

Behavior

• The warning appears on nearly every tool call (web search, MCP tools,

internal tools like artifacts).

• In most cases the tool actually executes correctly and the conversation

continues normally on the next turn — the banner seems cosmetic.

• One time the tool call genuinely failed with no output, but the very next

user message recovered the conversation without issue.

• Happens in brand-new chats as well as existing ones.

Not fixed by

• Restarting the desktop app
• Switching between desktop and web client

Happy to provide request IDs or a screen recording if useful.

Same issue. I'm currently using Claude Desktop on Windows with Sonnet 4.6. Local MCP servers are all running properly with no errors.

Same issue here. Claude Code works though, but the desktop app and web app fail to submit tool results.

<img width="554" height="105" alt="Image" src="https://github.com/user-attachments/assets/c7278d34-4f65-4524-8f38-a57d45fa52fb" />

Same issue on Claude.ai web April 22, 2026.

• Error: "Tool result could not be submitted. The request may have

expired or the connection was interrupted. Refresh the page to continue."

• Triggers on every tool call (web search, artifacts, file analysis).
• Happens in new chats and existing ones.
• Refreshing does not fix it error reappears on next tool call.
• This is NOT a Claude Code issue, it's Claude.ai web/desktop.

+1 to prioritize. Related: #51903

Same: Tool result could not be submitted. The request may have expired or the connection was interrupted. Refresh the page to continue.

Samere since this morning. Any resolution yet? "Tool result could not be submitted. The request may have expired or the connection was interrupted. Refresh the page to continue."

Same issue here on Macbook MacOs Tahoe Version 26.4.1 (25E253) - both on the desktop app AND in chrome browser.

<img width="529" height="78" alt="Image" src="https://github.com/user-attachments/assets/df3a0949-df6f-42d8-96ef-a71a967bf98e" />

This should be resolved now.

Yes, so am I on the morning of Thursday 23rd April 2026 near London, UK. In this case I am using the Windows desktop app, after previously using a Windows browser window and a Mac browser window.
________________________________
From: gyamfir @.*>
Sent: 23 April 2026 07:37
To: anthropics/claude-code @.*>
Cc: Gary Newport @.>; Comment @.>
Subject: Re: [anthropics/claude-code] [BUG] [Error] Tool result could not be submitted. (Issue #51874)

[https://avatars.githubusercontent.com/u/179041165?s=20&v=4]gyamfir left a comment (anthropics/claude-code#51874)<https://github.com/anthropics/claude-code/issues/51874#issuecomment-4302224813>

You sure it's resolved. Im still getting the error

—
Reply to this email directly, view it on GitHub<https://github.com/anthropics/claude-code/issues/51874?email_source=notifications&email_token=ALI4FOFQJHT3XB5637TK45L4XG23JA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMZQGIZDENBYGEZ2M4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4302224813>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALI4FOEX4U5V2TUZEJ2U7VL4XG23JAVCNFSM6AAAAACYB6PLC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DGMBSGIZDIOBRGM>.
You are receiving this because you commented.Message ID: @.***>

I've encountered again this morning "Tool result could not be submitted. The request may have expired or the connection was interrupted. Refresh the page to continue."

Having the samle issue in the llm webapp.(https://claude.ai/chat/)
If I ask to use a tool, any tool, I get the message. If I ask not to use a tool I don't get it.
Everything seems to work fine though.
Same issue with all available models btw.

Glad I'm not the only one. It's more of an annoyance than anything else. It's still doing everything it needs to do, just acting like it can't do it.

I am using Claude desktop on windows and facing same issue.

issue with custom mcp to my own vikunja setup, when i want to start a research, it asks me to confirm mcp connectors to use in research, i cant get the modal out of the way. keep seeing the error.

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.