---
title: "Messages"
url: "https://docs.teleflows.io/guides/mcp/reference/messages.md"
canonical_url: "https://docs.teleflows.io/guides/mcp/reference/messages/"
last_updated: 2026-10-01
type: reference
summary: "Messages the Teleflows MCP server can show and what to do about each one."
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/concepts/roles-and-access.md"
  - "https://docs.teleflows.io/guides/mcp/reference/limits.md"
---

# Messages

The server's messages are short and safe to show: they never contain your key. The assistant may repeat them in its own words.

## Sign-in page

| Message | What it means | What to do |
|---|---|---|
| That does not look like a Teleflows API key (it starts with tfk_). | The pasted text is not a Teleflows key. | Copy the whole key again from Teleflows. |
| Teleflows did not accept this key. Check that it is complete, active and not expired. | The key is incomplete, expired or revoked, or from another Teleflows environment. | Copy the whole key again, or [create a new one](https://docs.teleflows.io/guides/mcp/how-to/create-api-key/). Check the [server address](https://docs.teleflows.io/guides/mcp/concepts/server-address/). |
| The key could not be checked with Teleflows right now. Try again in a moment. | Teleflows did not answer the key check. | Try again in a moment. |
| Too many attempts for this sign-in. Start again from your app. | Several wrong keys in one sign-in. | Start the connection again from your app. |
| This sign-in has expired. Start again from your app. | The sign-in took too long or was already used. | Start the connection again from your app. |
| Finish the sign-in in the browser window that started it. Start again from your app. | The key was sent from a different browser or tab. | Start again from your app and finish in the window that opens. |
| Too many sign-in requests. Wait a minute and try again. | Many sign-ins in a short time. | Wait a minute and try again. |
| Too many sign-in attempts. Wait a minute and try again. | Many keys sent in a short time. | Wait a minute and try again. |
| This app is not registered with the Teleflows MCP server. | The app did not identify itself in a way the server accepts. | Start again from your app. If it persists, the app may not support this server. |
| The app's return address is not registered for this app. | The app asked to return to an address it did not register. | Do not continue. Start again from your app. |

## Answers to questions

| Message | What it means | What to do |
|---|---|---|
| Your Teleflows API key is invalid, expired or revoked. Create a new key in Teleflows under Settings → API keys. | The key stopped working after you connected. | [Create a new key](https://docs.teleflows.io/guides/mcp/how-to/create-api-key/) and connect again. |
| Your API key's role cannot use this. Ask a Teleflows admin for a key with more access. | The key's role cannot read this data. | Use a key with a role that can, or ask a Teleflows admin. See [Roles and access](https://docs.teleflows.io/guides/mcp/concepts/roles-and-access/). |
| … not found, or not visible to your API key. | The record does not exist, or your key's role cannot see it. | Check the name or ID, or use a key with more access. |
| No recording, or not visible to your API key. | The call has no recording, or your key's role cannot see it. | Use a key with more access if you expect a recording. |
| Cost (`total_cost_cents`) is not available for your API key's role. | Teleflows did not return the cost field for your key. | Nothing to do: the result shows the fields Teleflows returned. |
| The window is … days; the maximum is 31. … | The question covers more than 31 days. | Ask for the period in parts of up to 31 days. See [Limits](https://docs.teleflows.io/guides/mcp/reference/limits/). |
| since must be before until. … | The start of the period is not before its end. | Ask again with a valid period. `until` is exclusive. |
| … item(s) were left out to fit the size limit. … | The result was too large and was shortened. | Ask for fewer records, fewer details or a narrower filter. |
| This request needed more Teleflows reads or time than one tool call allows. … | The question needed too much work at once. | Narrow it: fewer details, a smaller period or a more specific filter. |
| Teleflows is rate limiting requests. Wait a moment and try again. | Teleflows asked the server to slow down. | Wait a moment and try again. |
| Teleflows is temporarily unavailable. Try again later. | Teleflows is down or busy. | Try again later. |
| Teleflows did not answer in time. Try again later. | Teleflows took too long to answer. | Try again later, or ask a narrower question. |
| Could not connect to Teleflows. Try again later. | The server could not reach Teleflows. | Try again later. |
| Teleflows rejected the request: check the time window (at most 31 days, start before end) or start again without a cursor. | Teleflows refused the period or the page position. | Ask again with a valid period, or start the list from the beginning. |
| Invalid input. … Check the tool's input schema. | The assistant sent an input the tool does not accept. | Usually the assistant corrects this itself. Otherwise rephrase the question. |
