Creating a project secret from inside the connect sheet's create-secret drawer fails with a server error on every attempt.
What was seen
Driving a key reconnect, the flow reaches a step offering to create a project secret without leaving the sheet. Submitting that form returned An unexpected error occurred with the operation identified as create_secret. It happened on every attempt, with a fresh secret name each time, so it is not a name collision.
The consequence for the flow it sits in: a person repairing a connection that needs a new credential cannot create one from where the product offers to create it, so the reconnect cannot be completed from that path.
What is not established
This was found while reproducing something else and was deliberately not investigated. In particular: whether the same request succeeds from the ordinary secrets screen rather than from inside the sheet, which would narrow it to the in-sheet path; and what the server-side error actually is, which is in the deployment's logs under that operation identifier.
Those two checks are the natural first steps and are cheap.
Why it is filed rather than chased
It blocked one live verification during the MCP gateway release's final pass and is unrelated to anything that release changes. It is filed so it is not lost, with an explicit note that nobody has looked at the server side.
Creating a project secret from inside the connect sheet's create-secret drawer fails with a server error on every attempt.
What was seen
Driving a key reconnect, the flow reaches a step offering to create a project secret without leaving the sheet. Submitting that form returned
An unexpected error occurredwith the operation identified ascreate_secret. It happened on every attempt, with a fresh secret name each time, so it is not a name collision.The consequence for the flow it sits in: a person repairing a connection that needs a new credential cannot create one from where the product offers to create it, so the reconnect cannot be completed from that path.
What is not established
This was found while reproducing something else and was deliberately not investigated. In particular: whether the same request succeeds from the ordinary secrets screen rather than from inside the sheet, which would narrow it to the in-sheet path; and what the server-side error actually is, which is in the deployment's logs under that operation identifier.
Those two checks are the natural first steps and are cheap.
Why it is filed rather than chased
It blocked one live verification during the MCP gateway release's final pass and is unrelated to anything that release changes. It is filed so it is not lost, with an explicit note that nobody has looked at the server side.