Docs / Help

Troubleshooting

Fixes for the most common problems with sign-in, knowledge ingestion, lens answers, the MCP server, and the developer API.

Find your symptom below. If nothing here matches, check the FAQ or write to hi@mindola.ai.

I can’t sign in

There are three ways into your account: your email and password, Continue with Google, or a one-time email link. If you forgot your password, choose Sign in with an email link instead on the sign-in page, enter your email, and open the link from your inbox. Once you are in, you can set a new password under Account then Profile.

The email link works for 30 minutes and can be used once. If it has expired or you already used it, request a new one. If you do not have an account yet, clicking the link creates one and verifies your email at the same time.

A source is stuck on “Indexing now…”

Sources show Indexing now… for a few seconds while they are read, chunked, and indexed. Give a large document a minute, then ask a question only that document could answer. The citation confirms it landed. See Adding knowledge for what each format becomes.

If an upload gets interrupted (your laptop sleeps, the browser tab closes), Mindola checks in the background. Sources that actually finished are marked Ready automatically, and anything that did not finish is marked Failed with a note to re-upload, so nothing sits in “Indexing now…” forever.

Two tips for heavy files: split a big PDF into shorter files, because smaller documents index faster and quote more precisely, and keep audio or video files under 25 MB each by splitting longer recordings into clips.

My lens doesn’t answer from a new source

Work through these checks in order:

  1. Is the source ready? Open Library or your Knowledge page and confirm the source shows as ready, not pending or failed.
  2. Is it in scope? A capture saved with no space still feeds your private chat, but it will not reach a lens that is scoped to a specific space. By default a lens reads everything in its workspace; check what it can see by opening Lens then Customize, under Access and What can this lens read? See Access and privacy.
  3. Is it something a lens refuses on purpose? Even inside its scope, a lens will not hand out sensitive details like addresses, phone numbers, passwords, or medical and financial information, no matter how a visitor phrases the question.

The fastest test: open your own lens link and ask a question only the new source could answer.

I can’t add new knowledge

Two different limits can stop new material:

  • Your word allowance is used up. When your lifetime allowance hits zero, uploads, files, links, and voice transcription stop, and a card explains what happened. Chat keeps working normally and nothing you already added is touched. Deleting a source you no longer need refunds the exact words it cost. See Word allowance.
  • You hit a daily upload cap. Some upload types are capped per day and reset daily. When you reach a cap, that tile on the Knowledge page turns into an upgrade link while the other tiles keep working. Your plan’s exact limits are shown in the app under Settings then Subscription; see Plans and billing.

The MCP server answers 405

Expected. A GET request with Accept: text/event-stream answers 405 because the server does not offer a server push stream. Some MCP clients probe for this on connect; it is harmless. A plain GET without that header returns a JSON info document. See MCP server.

Rate limit errors on the MCP tools

Anonymous use is rate limited per MCP session, with your IP as fallback: lens creation allows 2 per minute and 10 per hour, and the other two tools allow 20 calls per minute per IP. If you hit a limit, wait a minute and try again.

”Lens is claimed” errors from add_lens_knowledge

This tool only works on unclaimed lenses. Once you claim a lens by signing up through its claim URL, anonymous connectors can no longer modify it. Make further changes in the app at https://app.mindola.ai, or through the authenticated developer API. See Instant lens for how claiming works.

401 from the developer API

Your mnd_ key is missing, malformed, or revoked. Check that the Authorization: Bearer header carries the full key. Keys are shown only once at creation, so if you lost it, create a new one in the app.

429 from the developer API

Write endpoints allow 30 requests per minute per key. Slow down and retry.

Still stuck

Read the FAQ, or email hi@mindola.ai with enough detail to reproduce the problem.