# not_found

> The game does not exist, or the credential in use may not publish to it.

| | |
| --- | --- |
| Kind | `disko` command error |
| `disko` exit code | 3 (auth) |

`disko publish` reports `not_found` when the registry answers `404` to the
upload. The registry gives the same answer whether the game does not exist or
the credential may not publish to it, so the two cases look alike. The command
exits with code 3.

When a CLI token is in use and `disko` can tell that the game exists, it
reports [missing_permission](/errors/missing_permission) instead, because the
token must be the problem.

## Fix

- Check that `game` in `game.json` matches the game address shown in the
  Creator Portal, including the namespace.
- Create the game in the Creator Portal if it does not exist yet. The CLI cannot
  create games.
- With a CLI token (`DISKO_TOKEN` or `disko login --with-token`), check that
  the token has the `publish` permission for this game or for all games.
- With browser sign-in, check that you are signed in to the account that owns
  the game. Run `disko logout` and `disko login` to switch accounts.

## See also

- [Games and namespaces](/registry/games-and-namespaces)
- [CLI tokens](/registry/cli-tokens)