Troubleshooting
The cockpit tells two situations apart. It could not look: the request failed, so nothing is known. Or it looked and found nothing: the answer came back and was empty. The messages below are the exact English wording. Check which of the two a message describes before you act on it.
Signing in
| Message | What it means | What to do |
|---|---|---|
| Single sign-on is unavailable — the sign-in service could not be reached. You can still sign in with your email and password. | The cockpit could not reach the sign-in service’s configuration. | Sign in with your email and password, or try again later. |
| The server did not accept these credentials. | The email or password was rejected. | Check both and try again. |
| Invalid two-factor code | The code from your authenticator was wrong or out of date. | Wait for the next code and enter it. |
| MFA session expired — please sign in again | The second-factor challenge timed out. | Sign in again from the start. |
| This account is not authorized for this instance | Your account is valid but has no access to this instance. | Ask an admin of the instance to invite you. |
| Session expired — please sign in again | Your session ended. | Sign in again. |
| No instance grants you access | You signed in, but you hold no grant on any instance. | Ask an admin to invite you. |
| Could not be read, on the instance picker | The instance list could not be read. This does not mean you have none. | Select Retry. |
No data yet
| Message | What it means | What to do |
|---|---|---|
| Nothing is connected yet | No data source is attached to this instance, so there is nothing to assess. | Select Connect a data source, or see Connections. |
| No data source is configured yet. | The source list was read and is empty. | Select Connect a data source. |
| Could not load your data sources. | The source list could not be read. | Select Retry. If cached sources are shown, they may be out of date. |
| Run a session fetch first — this twin analyzes that instance’s real findings. | The twins analyse the session fetch, and none has completed yet. | Open Fetch and wait for the session fetch, or run a fetch yourself. |
| Unable to Assess | The twin answered, but could not produce an assessment. This is not a clean result. | Read the spoken summary for the reason. Usually you need to connect a data source and run it again. |
Fetch
| Message | What it means | What to do |
|---|---|---|
| Offline mode: Fetch task queued for background synchronization. | The cockpit could not reach the server, so it kept the run on your device. | Nothing. The run is sent automatically when the connection returns. |
| Offline queueing failed: {error} | The run could not even be queued. | Try again once you are back online. |
| No result received | The run ended without a final answer. | Open the run to read what arrived, then ask again. |
| Your last fetch failed. | The last run did not complete. | Select Open the run and read Result and Error. |
| Failed to load fetch starters | The prepared questions could not be loaded. | Type your question instead. |
| This run is no longer in your history. | The run was deleted or the history was cleared. | Nothing to recover. Run it again. |
Twins and Simulate
| Message | What it means | What to do |
|---|---|---|
| Failed to fetch action queue: {error} | The approval queue could not be read. It may not be empty. | Select Refresh. |
| That file is too large to analyze (3 MB maximum). | The file for Analyze document is over the limit. | Split the file or reduce it. |
| Could not read that file. | The browser could not read the chosen file. | Pick the file again. |
| Could not load scenarios | The simulation scenarios could not be read. | Select Retry. |
| Failed to extract rules: {error} | Rule extraction could not run. | Select Retry on Reconcile. |
Voice and media
| Message | What it means | What to do |
|---|---|---|
| Voice input is unavailable in this browser or the microphone was blocked. Type your question instead. | The browser has no speech support, or microphone access was refused. | Allow the microphone for the cockpit’s site in your browser settings, or type instead. |
| Voice error: {error} | Dictation stopped with an error. | Try again, or type the question. |
| Call failed | The voice call could not be set up or dropped. | Read the reason under the status, then select Start call again. |
Still stuck
- Check the Support Log for what happened in a call.
- For deployment-side problems, see Operations.