When something fails, DataMind Oda says so in the chat and keeps what already happened. This page collects the failure notices you may meet in a chat, what each one means, and how to carry on. The chat itself is covered in Chat with Oda, and the way a turn runs and ends in Sessions and the transcript.
A turn that ends in a failure shows its own row in the chat:
This turn failed, with the reason beside it and, when there is one, a code.A turn you stopped is not a failure. It keeps its Stopped marker and Oda does not carry it on; Stopping Oda and queued messages and The chat transcript cover stopping. A tool call that was still running when the turn was stopped is kept as an interrupted result, named Interrupted; Oda's steps and tool results shows how a stopped step looks.
A model request rejected for an authentication reason shows API key is invalid with the code AUTH. The model service's own error text is not shown in the chat; the session log keeps the diagnostic. If the model comes from a provider you configured, check the provider's sign-in in Settings > Models (Set up models and providers); otherwise ask your administrator.
When a model request fails for a reason that can pass, Oda retries it on its own before the turn gives up. A retry row in the turn tells you where it stands:
Waiting to retry model request: the next attempt is waiting. The row counts down to it and shows which attempt it is, formatted like {label} ({retry}/.Retrying model request: an attempt is running now.Retried model request: a retry has run.Model request retry cancelled: the retry was cancelled before it ran, because its step or the turn closed first, for example when you stop the reply.∞ in place of the maximum.Retry delay: and Failure reason:.You do not need to do anything while a retry waits. If the retries do not fix the failure, the turn ends and its failure row appears.
If the model reaches its output limit, the reply stops part-way and a warning row follows, marked with an amber warning dot: Output token limit reached. The row says what to do: The reply was cut off; earlier output is preserved in the conversation.
Send continue as your next message, and the model carries on where it stopped. The notice sits before the turn's closing actions, so the actions under the answer, such as Copy and Branch into a new conversation, stay available. Reading Oda's answers shows this row with the other notices a turn can carry.
A request needs a working DataMind sign-in. When the sign-in has ended or no longer works, the reply fails and the chat shows a short sentence with a code, such as DATAMIND_PASSWORD_CHANGED or DATAMIND_ACCESS_DENIED. Keep the code when you ask for help.
| The chat shows | What it means | What to do |
|---|---|---|
Your password changed. | Your DataMind password was changed, so the old sign-in no longer works. | Sign in to DataMind again. |
You were signed out on all devices. | The sign-in was ended on every device. | Sign in to DataMind again. |
Your DataMind sign-in ended. | The saved sign-in is no longer valid. | Sign in to DataMind again. |
Your DataMind password has expired. | The password behind the sign-in has expired. | Change your password in the DataMind web app, then send the message again. |
DataMind refused access: {reason} Ask your administrator. | DataMind refused the request for your account; the reason comes from your server, for example No active role. | Ask your administrator. |
The DataMind sign-in service is not available. | The service that handles DataMind sign-ins is not reachable right now. | Try again in a moment; if it keeps happening, contact your administrator. |
Your DataMind sign-in could not be renewed. | The sign-in could not be renewed. | Check the connection to your DataMind server, then send the message again. |
Sign in again the same way you did the first time: Sign in to Oda. Your chats are kept. How Oda keeps the sign-in alive day to day is on Signing in and staying signed in.
This turn failed. What should I do?Send the request again, or continue with something else in the same chat. If the same failure keeps coming back, keep the message and the code beside it and contact your administrator; Troubleshooting lists the messages Oda can show and what to do about them.
No. A stop is an ending you chose: the turn keeps its Stopped marker and Oda does not carry it on. A failure is Oda's ending, shown as This turn failed.
A model request can fail for a reason that passes, and Oda tries it again before the turn gives up. The retry row shows where it stands; open it to read Retry delay: and Failure reason:. You do not need to do anything while a retry waits.
The row tells you: it shows the attempt out of the maximum, formatted like {label} ({retry}/. A session that retries without a set limit shows ∞ in place of the maximum.
No. A retry that is still waiting is cancelled when its step or the turn closes, for example when you stop the reply. The row then reads Model request retry cancelled.
The sign-in Oda uses has ended or no longer works, so the request that needed it failed. The chat shows which case it is: your password changed, you were signed out on all devices, or the sign-in simply ended. Sign in again and send the message; your chats are kept.
DataMind refused access mean?Your DataMind server refused the request for your account, and the reason it gives is shown with the message, for example No active role. Ask your administrator to check your access.
API key is invalid?The model request was rejected for an authentication reason, and the failure is shown with the code AUTH. The model service's own error text is not shown in the chat; the session log keeps it. If the model comes from a provider you configured, check the provider's sign-in in Settings > Models (Set up models and providers); otherwise ask your administrator.