Troubleshooting

Release status

Outcome

Identify whether a problem is authentication, an expired device request, a service read failure, or an unreleased capability.

Prerequisites

1. The exact error message
2. The original localized return path
3. Access to the CLI device when approving a code

Current path

1. For sign-in failures, restart from the website sign-in action and verify that the callback returns to the same localized OpenToken origin.
2. For an invalid device code, begin a new request in your own CLI; codes expire after ten minutes and are single-use.
3. For unavailable account state, retry later. Failed reads do not change device, sharing, or credential state.
4. For Development or Planned features, wait for a published release instead of guessing commands or endpoints.

Authoritative success state

The account or device page displays an authoritative result, or the product accurately identifies the state as unavailable.

Common failures and recovery

1. Approve only a request you started on your own CLI.
2. Never paste device credentials, API keys, or OAuth responses into support messages.

Security and privacy boundary

Error reports should omit secrets, private model names, and native application content.

Next valid action