Troubleshooting

The connector is not connected. Installing the Promethist plugin does not connect it: open the plugin’s Connectors tab, enable the connector of your region and choose Connect (Connecting Claude). In Claude Code, run /mcp and authenticate the server.

The sign-in lapses after 30 days without use, or when Promethist has to renew its signing keys. Sign in again; nothing else is lost.

You are connected to the other region, or you signed in with a different Promethist user than the one you use in the Studio. Accounts exist in one region only.

The Promethist MCP server supports Claude. Its sign-in accepts only Claude’s own callback addresses and callbacks on your own computer, and its endpoint refuses browser requests from other websites.

Your role in that account or project does not allow the operation — for example a Viewer asked for a change. An Owner of the account or project can give you a stronger role (Sign-In and Permissions).

Expected: the operation removes something and needs your confirmation. Claude asks you and repeats the call.

Claude tried to set something the tool does not support. Nothing was changed; the message lists what the tool accepts, and Claude normally corrects the call itself. If it keeps failing, the change may not be possible through Claude — use the Studio.

The tool or guide is for Promethist staff (Reserved for Promethist Staff). There is no role to request.

A temporary failure on the platform. Try again; if it persists, contact Promethist support with the time of the attempt.

A fault on Promethist’s side, already logged. Contact Promethist support if it blocks you.

Test conversations through Claude run without a signed-in end user, and drafts are not run for such conversations. Promote the draft to preview — Claude asks before doing so — and test that revision.

The message names each scenario that cannot run. An agent that is not pinned to a revision needs a published revision; a pinned revision must be a preview or published one, because drafts are not run in test conversations. Publish the agent or pin its preview revision in the scenario, then start the suite again.

Test-suite conversations carry no signed-in user, so a project that requires sign-in, or enforces external roles, under Identity providers would turn every one of them away. The suite is refused before anything starts. Test such a project’s agents in a signed-in session instead — Open in new Tab on the agent’s page in the Studio.

For such projects the server signs live tests in with a Promethist test identity. When that identity is not set up in your region, or not admitted to the project, Claude tells you so. Test the agent in a signed-in session instead, as above, and let Promethist support know.

A live test keeps its connection to the agent for the whole conversation and closes it after four minutes without a new message. Continuing later reconnects to the same conversation: the agent still has the messages, but not the plan it had made for them, so its next replies may differ. Start a new conversation for a clean test.

Check the account’s subscription first (get_subscription): agents do not serve end users while the subscription is not active.

The account’s Display full conversation data setting is off, or — for the raw-data tools — you are a member of a project but not of the account (What Conversation Data Claude Can Read).

Test conversations are left out: test-suite runs always, simulated users unless you ask about one specifically. So are the conversations of Promethist staff accounts, for example from when Promethist helped build or demonstrate your agents. The conversation list leaves them out as well.

Export links expire after 24 hours and upload links after one hour or their first use. Ask Claude to create a new one.