---
title: "Troubleshooting"
url: "https://docs.teleflows.io/guides/mcp/troubleshooting.md"
canonical_url: "https://docs.teleflows.io/guides/mcp/troubleshooting/"
last_updated: 2026-10-01
type: troubleshooting
summary: "Fix common problems when connecting to the Teleflows MCP server or asking questions."
related:
  - "https://docs.teleflows.io/guides/mcp/how-to/create-api-key.md"
  - "https://docs.teleflows.io/guides/mcp/concepts/server-address.md"
  - "https://docs.teleflows.io/guides/mcp/reference/messages.md"
---

# Troubleshooting

| You see | Why | What to do |
|---|---|---|
| Claude says "wasn't connected" right after signing in | The page shows an earlier status; the sign-in itself completed. | Reload the page. The connector is usually already connected. |
| "Teleflows did not accept this key" | The key is incomplete, expired or revoked. | Copy the whole key again, or [create a new one](https://docs.teleflows.io/guides/mcp/how-to/create-api-key/). |
| "Teleflows did not accept this key" with a key you just created | The key is from another Teleflows environment. | Use a key from the Teleflows environment the server reads. See [Server address](https://docs.teleflows.io/guides/mcp/concepts/server-address/). |
| "Too many attempts for this sign-in" | Several wrong keys in one sign-in. | Start the connection again from your app. |
| "Your API key's role cannot use this" | The key's role cannot read that data. | Use a key with a role that can, or ask a Teleflows admin. |
| An empty answer | No records in that period, or the role cannot see them. | Try another period, or check with a key that has more access. |
| The assistant stops working after some weeks | The key expired, or the connection reached 90 days. | Connect again. Create a new key if it expired. |

Every message and what it means: [Messages](https://docs.teleflows.io/guides/mcp/reference/messages/).
