# Troubleshooting > The nine Emolysis error codes and what to do about each, plus common problems with sign-in, tests, deploys, links and MCP. This page lists the common problems and how each is reported. Every command, on every surface, returns either a result or a typed error with one of nine codes. Start with `emo doctor` when something is wrong with your setup. ## Start here 1. Read the error's **code** first. It tells you which kind of problem it is. The message and details say more. 2. Run `emo doctor`. It checks the engine, DuckDB, the credential store and whether a model key or plan is configured, and each failed check says what to fix. 3. If the problem is on your platform, read the platform's own message in the error details. 4. If a golden test fails, read the differing rows, not just the failure. ## Error codes | Code | What it means | What to do | | ---------------------- | ------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `invalid_params` | A parameter is missing, has the wrong type or is not allowed | Check the command's parameters with `emo commands --schemas` | | `not_found` | A table, template, project or link does not exist | Check the name and the connected workspace | | `not_implemented` | The command exists but is not built for this case yet | Use another platform or shape, or wait for support | | `auth_required` | You need to sign in, or your session expired | Sign in again; confirm the code in the browser | | `platform_error` | Your platform returned an error | Read the platform's message in the details | | `conflict` | The action clashes with the current state | Refresh, then retry | | `internal` | Something failed inside Emolysis | Retry; if it repeats, include the details when you report it | | `insufficient_credits` | No included usage or usage credits are left | Wait for the limit to reset, switch to your own key, move to a plan with more included usage, or turn on usage credits. On Enterprise, ask an admin to raise your spend limit | | `rate_limited` | Too many requests in a short time | Wait the seconds the error gives, then try again | The [error codes](https://emolysis.com/docs/error-codes) page explains each one in more detail. ## Common problems ### Sign-in - **The sign-in code expired.** Codes expire after 15 minutes. Run the command again for a new code. - **Your editor says you need to sign in.** Every tool needs an Emolysis account, local files included. Confirm the code in the browser, or run `emo login`, then retry the call. ### Golden tests and deploys - **Golden tests fail after you changed a slot.** Read the differing rows in the test output. A changed key or ordering column often changes which row "wins". Fix the slot, or update the expected output if the new behavior is what you want. - **Tests pass on DuckDB, deploy fails.** The platform rejected something DuckDB accepted, often a permission. On Databricks, check Unity Catalog grants for the catalog and schema, and whether the job runs on serverless or classic compute. The error details carry the platform's message. See [Golden tests on DuckDB](https://emolysis.com/docs/golden-tests). - **Identifiers not found on Snowflake.** Unquoted identifiers fold to uppercase there. Use the case the profile expects, or quote consistently. ### Catalog and samples - **The catalog looks out of date.** The local mirror is refreshed on request. Refresh the connection after schema changes on your platform. - **Samples are slow or large.** Pull fewer rows or only the columns you need. Samples are for looking at results; golden tests use the fixtures in `tests/`. ### Dashboards - **A dashboard link asks you to sign in.** Without signing in, a link that is limited to an organization or to one person looks the same as a link that points to no dashboard, for example a mistyped one. Check that the link was copied in full. Signing in on this website is not open yet, so a link like this opens in the Emolysis app, with an account that has access. See [Sharing dashboards](https://emolysis.com/docs/sharing). - **A dashboard link says it was revoked, has expired or was not found.** Revoked and expired links each show their own message; ask the person who shared it for a new link. "Not found" means there is no dashboard at the link, or, once you are signed in, that it is not shared with you. - **A refresh with publishing on stops because the dashboard's link is gone.** The link was revoked. A refresh never makes a new link: publish the dashboard from the app, which makes one with a new URL, and send that link on. - **Publishing stops because the link's setting is fixed.** You asked for a different setting from the one the link has. Revoke the link, then publish again with the setting you want. See [Sharing dashboards](https://emolysis.com/docs/sharing). - **A chart shows an error instead of a drawing.** Its spec broke a rule, for example a pie with two measures. The other charts still draw. See [Chart types](https://emolysis.com/docs/chart-types). ### Editors and models - **Your editor does not show Emolysis tools.** Check that `emo` is on your path, that the MCP entry runs `emo mcp`, and restart the client. `emo doctor` checks the engine itself. See [The MCP server](https://emolysis.com/docs/mcp-server). - **Model requests fail.** Check that your key is set and valid, or that your plan's included usage or usage credits cover the request. The provider's own error message is in the details. See [Model keys and credits](https://emolysis.com/docs/model-keys-and-credits). ## Reporting a problem There is no product support yet. For questions about this site or the design, write to [hello@emolysis.com](mailto:hello@emolysis.com); the [support page](https://emolysis.com/support) lists what exists today. For the public repositories, [emolysis/template-sdk](https://github.com/emolysis/template-sdk) and [emolysis/integrations](https://github.com/emolysis/integrations), open an issue there. Never paste credentials, keys or real data into an issue or an email. If you include an error, include its code and details, and remove anything private first. --- Page: https://emolysis.com/docs/troubleshooting. Emolysis is a product of Bandpey GmbH, Munich, Germany. It is in private development, and nothing is released yet.