> For the complete documentation index, see [llms.txt](https://docs.katara.ai/about/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.katara.ai/about/reference/troubleshooting.md).

# Troubleshooting

Start by identifying the organization, resource and operation that failed. A successful login, upload receipt or configuration save does not prove that the next operation is ready.

## Access and onboarding

| Problem                                            | Next step                                                                                                                                                |
| -------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Invitation does not work with my account           | Sign in with the invited email and confirm the invitation. Ask an administrator to inspect invitation status rather than sharing another person's login. |
| I can use MCP but cannot open the dashboard        | Check whether your role is MCP User. That role intentionally provides read-only MCP access without business-dashboard access.                            |
| A menu or action is missing                        | Confirm the selected organization and your current role/capabilities. Brain and document authority are checked separately.                               |
| Dashboard redirects to onboarding or payment setup | Complete the required organization/subscription steps. Ask an administrator to resolve failed subscription lookup or payment state.                      |
| I am an administrator but cannot see a Brain       | Organization administration does not grant ownership of every private Brain. Ask the owner to grant appropriate Team access.                             |

## Uploads and knowledge

**A file was accepted but is not available for answering.** Check the per-file result first, then the relevant collection synchronization or Brain refresh and search readiness. Upload acceptance is not completed indexing. The UI does not report every extraction/indexing stage per file.

**I cannot select a Brain as the destination.** Confirm it is initialized and ready, enabled, and that you have current contribution authority. Contribution disclosure must be available so you can review audience and export exposure. A connection or permission error is not permission to bypass that disclosure.

**I cannot attach an existing document to a Brain.** Brain source membership follows direct ingestion origin. Upload the intended file directly through the Brain's source workflow; a collection filter or sharing change does not convert the origin.

**Wiki content is stale after a source change.** Inspect freshness and refresh activity. A request may be queued or failed. Do not repeatedly request refreshes without checking the current run, and do not treat a new refresh as replay of an old run.

**A search did not find my Brain, file or fact.** Some UI searches cover loaded items, not the entire organization. Use pagination or load more where available. Active fact recall is bounded and is not a complete historical inventory.

See [Sources](https://docs.katara.ai/about/brains/sources.md) and [Activity](https://docs.katara.ai/about/brains/activity.md).

## Editing and facts

**Edit page or Manage facts is unavailable.** Check deployment availability, contribution authority and whether the selected page has current readable revision metadata. For contributions, validate an enabled Q\&A alias bound to the exact Brain. Ordinary Wiki reading does not need that alias.

**A save conflicts with another change.** Load the latest canonical content through the offered recovery action, compare it with your draft and deliberately reapply your changes. Do not assume a refresh overwrites the server or repeatedly submit a stale revision.

**A fact correction partially completed.** Replacement and retirement are separate outcomes. If the replacement was accepted but retirement failed, retry the unfinished retirement through the offered flow instead of adding the replacement again.

See [Knowledge and pages](https://docs.katara.ai/about/brains/knowledge.md) and [Facts](https://docs.katara.ai/about/brains/facts.md).

## Answers and exports

**The answer uses the wrong knowledge.** Inspect the Q\&A agent's configured Collection or Brain. There is no per-question target switch. A saved Brain-backed binding cannot be changed; create another agent for a different Brain.

**A question set to Real-time does not generate a fresh answer.** The current interface treats Real-time like Blocked. Do not rely on that option as a cache bypass.

**GitHub did not update after I saved settings.** Configuration, owner acceptance, export request and completed export are separate steps. Inspect export history and verify current destination/credential approval. Transfer or recovery pauses export until the new owner supplies fresh credentials and consent.

**Deleting a source did not remove material from GitHub.** Existing derived content and exported history can persist. Source deletion is not external history erasure. Review the export's history disclosure before using sensitive material.

See [Q\&A agents](https://docs.katara.ai/about/agents-and-answering/qna.md) and [GitHub export](https://docs.katara.ai/about/brains/github-export.md).

## Get useful help safely

Provide the operation, approximate time, selected organization, resource identifier, visible error, and relevant run identifier when available. Explain whether the result was rejected, accepted, queued or completed. Share screenshots only after removing confidential content.

Never include access tokens, repository tokens, one-time passwords, full API-grant JWTs or private source text in a support request. For deployment-specific unavailable features, include the [availability category](https://docs.katara.ai/about/reference/availability.md) rather than assuming the failure is a user-permission problem.
