> ## Documentation Index > Fetch the complete documentation index at: https://docs.glood.ai/llms.txt > Use this file to discover all available pages before exploring further. # Troubleshooting > What went wrong, what it means, and what to do about it ## Connecting | What you see | What it is | What to do | | ------------------------------------------------------------ | ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------- | | The browser opens, you approve, and the client keeps waiting | The approval never reached the client | Try connecting again. If it repeats, report it — this one is ours to fix, not yours | | "Your assistant's access has expired" | Unused for over 30 days, or the connection was revoked | Reconnect from your client | | The assistant does not know what `whoami` is | The server is connected but the skills are not loaded | Re-run `npx skills add LoopClub/glood-agent-skills` and start a new session. See [Install the skills](/platform/skills) | | Your client will not connect at all | It may not speak MCP authorization | Check the requirements in [Connect any MCP client](/platform/mcp-server) | | A Custom GPT will not authorize | Custom GPTs cannot register themselves | That path needs credentials from us — email [support@glood.ai](mailto:support@glood.ai) | ## Seeing your data | What you see | What it is | What to do | | ------------------------------------------------------------ | ---------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- | | It cannot see an organization you belong to | You did not tick it when connecting, or you joined it afterwards | Add it at Account → Connections | | A store you own is not found | It may still be a draft — its install never finished — or it was not ticked when you connected | Finish connecting it, or add its organization at Account → Connections | | "no Glood app connected" on a store you use | That store has no Glood app syncing events, so nothing has been collected to report on | Connect Glood Search or Glood Personalization to it | | "Your role does not allow that" | Your role in **that** organization, not a connection problem | Ask an admin to change your role there | | Asking about two organizations at once fails | Deliberate — currencies, timezones and roles differ between them | Ask one organization at a time | | "read-only" when you asked it to change something in Shopify | Deliberate: this connection reads your Shopify data and never writes it | Make the change in Shopify admin; the assistant will tell you where | | A change that asks you to confirm | Archiving, stopping a deployment and removing a schedule are two-step by design | Read the review it shows you, then say yes | ## Errors your assistant may quote Occasionally an assistant repeats the error code it got back. These are what they mean. | Code | What it means | | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------- | | `FORBIDDEN` | Your role in **that** organization lacks the permission. The message names which one. | | `CROSS_ORG_SCOPE` | One call named stores in two organizations. It needs splitting into one call per organization. | | `APP_NOT_ENABLED` | No Glood app on that store can answer that report. Connecting Glood Search or Glood Personalization is what starts collecting those events. | | `STORE_NOT_FOUND` | Not reachable by this connection — another organization's, not granted, still a draft, or removed. | | `REPORT_NOT_FOUND` | That report name does not exist. Ask what reports the store can answer. | | `ORG_NOT_FOUND` | That organization is not shared with this connection. | | `AMBIGUOUS_TARGET` | A name matched in two organizations. The error lists the candidates — pick one. | | `VALIDATION` | The arguments were wrong: an inverted window, a missing field. The message names the field. | An error is an answer, not an outage. Every one of these is something you or the assistant can act on — none of them mean Glood is down. ## Numbers that look wrong Before assuming a figure is wrong, check what the assistant said around it. * **Did it name the window?** If not, ask. A shortened window is the single most common reason a number surprises someone — your data may not go back as far as the question did. * **Did the result carry a note?** "the top few, not everything" and "unavailable rather than zero" both change what the number means. See [How to read the answers](/platform/using#how-to-read-the-answers). * **Does it disagree with the dashboard?** It should not be able to — the same code computes both. If it does, report it. ## Still stuck Email [support@glood.ai](mailto:support@glood.ai). Including the exact question you asked and the error the assistant quoted makes it much faster to answer.