Troubleshoot Muse

Cause: no Muse administrator has saved a provider key. The chat shows "Nenhuma chave de provedor configurada." (No provider key configured.)

• Administrator: use the Configurar agora (Configure now) link (or open Settings in Muse) and save a key in one of the provider cards.
• Confirm the unlocked models in Modelos disponíveis (Available models).
• Without administrator permission, ask for the setup — the chat points the way: "Peça a um administrador do Muse para configurar." (Ask a Muse administrator to configure it.)

Cause: your Acesso ao Muse (Muse access) is set to Sem acesso (No access). Opening the Muse URL directly redirects to the team's home page. Fix: ask whoever manages the team to set Acesso ao Muse to Usuário (User) or Administrador (Administrator) in Settings → Members.

Cause: these screens belong to Muse's Administrador (Administrator) level only; with the Usuário (User) level, the URL redirects to Chat. Fix: ask for the Administrador level, or ask an administrator to do the configuration.

Cause: your individual monthly limit hit the cap set in Limites por usuário (Per-user limits). The typed message is discarded — copy the text before closing and resend it later.

• Ask an administrator to raise your value in Limites mensais de uso (Monthly usage limits).
• Or wait for the month to turn over, when consumption resets to zero.

Cause: the daily per-user limit — separate from the monthly one — hit its cap. It appears in the Hoje (Today) column of Seu uso este mês (Your usage this month) and isn't configurable in Limites mensais de uso (Monthly usage limits). Fix: wait until the next day; the daily limit resets automatically.

Cause: the Limite total do time (Team total limit) was reached — the block applies to every user. Fix: an administrator raises the value in Limites mensais de uso (Monthly usage limits) and clicks Salvar limites (Save limits), or the team waits for the month to turn over.

Cause: there are two gates — the module's skill and your scope in it. One closed gate is enough for the answer to come back empty.

• Administrator: confirm the module's switch in Skills do Muse (Muse skills) → Módulos disponíveis (Available modules).
• Confirm your user has scope in the queried module — without Closure access, you don't see tickets even with the skill on. See manage members.

Cause: the conversation is tied to the provider chosen at creation, and that provider's key was removed.

• Administrator: save a new key for the provider in Settings to reactivate the conversations.
• Or start a new conversation with an available model — you can't change the model of an existing conversation.

Cause: the Expira em (Expires in) countdown hit zero, or the proposal lost its validity before the decision. Fix: ask Muse for a new proposal in the same conversation and decide before the deadline.

Cause: the action requires a scope your user doesn't have — the Wiki draft, for example, requires administrator or editor scope in the Wiki. Fix: ask whoever manages the team for the required scope and generate a new proposal.

Cause: the streaming connection dropped mid-answer. Fix: reload the conversation to see the saved portion and resend the question if you need the rest. This differs from the Parar (Stop) button, which discards the partial answer from the screen.

Cause: the conversation's model doesn't support reasoning. Fix: start a new conversation with a compatible model — Claude with extended thinking or an OpenAI reasoning model.

Expected behavior: Muse's cost is the team's own AI provider bill, charged in USD ($X.XX). It doesn't mix with the Movitera® invoice.

Expected behavior: there is no renaming, archiving, or deleting conversations, and the title is generated automatically. To find a conversation, use ⌘K and type at least 2 characters of the title — the Conversas (Conversations) group lists up to 8 results.

Cause: the panel compares the monthly limit with the consumption of the filtered period — with Últimos 3 meses (Last 3 months), the bar can exceed 100% with no real block. Fix: select Mês atual (Current month) in Período (Period); chat blocking considers only the current month.

Cause: sending with context requires a Closure ticket or a Forge issue open at that moment. Fix: open the record and call ⌘K again; with no record open, press Enter alone.

Expected behavior: Muse never reveals passwords. Open the credential in Vault to view the secret.