Connector operations intermittently become "Resource not found" after several successful calls

For the last ~5 days, connector calls have been failing intermittently.

A given operation works correctly several times in a row.
After some number of successful invocations, the next call suddenly fails with no response, on MCP server side I see no requests happening.
Once this issue occurs, even previously working calls to the same operation start failing in the same way, until end of the agent operation.

Interrogation of the agent reveals that is getting error in response of tool invocation:

{
“error”: “Resource not found: /…/add_node. You can retry your request with an available resource. Your available resources are: \n\n{“finite”: true}”
}

When asked agent to repeat the operation it works for a while until it starting to error in the same way again - no Connector reset/reloads required.

This bug randomly kills access to connector operations mid-session, so longer automated flows can’t be trusted to finish and often have to be completed manually. Each failure also wastes tokens on retries, re-discovery of available operations, and extra explanation/debug messages, making even simple tasks more expensive than they should be.

4 Likes

Im not sure if Codex CLI category matches where it actually happens. Issue Im having is on the ChatGPT Plus plan + enabled Developer mode using MCP connector. This happening even with MCP connector with no auth enabled. Is this related to the Codex CLI too? Anyone got similar issues using MCPs over CLI?

This topic was automatically closed after 24 hours. New replies are no longer allowed.