Most problems come from the connection to your company's DataMind server or from a permission your account does not have yet. Find the message Oda shows below, or the question that matches your situation.
A request that needs your company's server fails until your sign-in works again; some companies supply the connection settings for their people, so signing in is all that is needed. If your company's server restarts, requests can fail for a short time and recover on their own.
When Oda will not start
You see
What it means and what to do
DataMind Oda is unavailable with The application could not start or stopped unexpectedly.
The app failed to start, or stopped unexpectedly. Close every other copy of Oda, then choose Restart. If it repeats, choose Disable third-party plugins, back up profile patch, and restart. Reinstall only as a last step.
Another copy of DataMind Oda is already running. Close it, then restart DataMind Oda.
Oda's local address is already in use by another copy. Close every other DataMind Oda window, then choose Restart.
DataMind Oda could not start, with the note If application files are missing or damaged, close the application and reinstall it. Your tasks are stored separately.
The app failed before its recovery dialog could appear. Reinstall DataMind Oda from your DataMind server; your chats, tasks, settings and plugins are stored separately and are kept. The steps are in Install and sign in.
The recovery operation failed
The chosen recovery action did not finish. Choose Exit and open Oda again, or try another option.
startup failed: 1 required plugin did not activate
A plugin stopped the start of the app. Choose Disable third-party plugins, back up profile patch, and restart.
Paste the DataMind URL from the DataMind Oda card in your company's DataMind OS. There is no API key to enter.
Could not reach this server. Check the address and your connection, then try again.
Check the address and your network connection, then try again.
This address is not a DataMind server. Check the address with your administrator.
Check the DataMind URL with your administrator.
This DataMind server does not support this version of DataMind Oda. Ask your administrator.
Oda offers the update without signing you out; take it. If no update is offered, ask your administrator.
This connection is not encrypted for an http:// address, continuing only with Continue without encryption
Ask your administrator for your server's https:// address. Continue only on a network you trust.
The security certificate of this server is not trusted by this computer, so DataMind Oda will not connect. Ask your administrator to install a trusted certificate.
Ask your administrator to install a trusted certificate. Oda does not connect without one, and there is no certificate bypass.
Sign-in was cancelled. Continue to try again., Sign-in timed out. Continue to try again. or Sign-in did not complete. Please try again.
Start the sign-in again and finish it in your browser; if the browser did not open, use Open again or Copy link.
Your DataMind sign-in has ended. Sign in again to continue. or Your DataMind sign-in ended. Sign in again.
Sign in again with your DataMind OS account. Your chats are kept.
Your password changed. Sign in to DataMind again. or You were signed out on all devices. Sign in to DataMind again.
The sign-in ended for a security reason. Sign in again with your DataMind OS account.
Your DataMind password has expired. Change it in the DataMind web app, then try again.
The password behind the sign-in has expired. Change it in the DataMind web app, then send the message again.
Your DataMind sign-in could not be renewed. Check the connection to your DataMind server.
Check the connection to your server, then send the message again.
Sign in to your DataMind server first.
A request needed your server with no working sign-in on this computer. Sign in again to continue.
DataMind refused access: {reason} Ask your administrator.
Your account cannot make this request; the reason from the server is shown. Contact your administrator with the reason.
The DataMind sign-in service is not available.
The sign-in service did not answer. Try again in a moment; if it keeps happening, check the connection and contact your administrator.
This session is already in use, possibly by another running DataMind instance (such as the web app or the desktop app). Quit the other running instances and try again.
The chat is held by another running copy of Oda. Quit the other running instances and send again; your draft is kept.
Sign-in required; reopen the address the server printed when it started.
Your browser opened the web app without a sign-in. Reopen the exact address Oda printed when it started the web app; if it is gone, start the web app again. See DataMind Oda in your browser.
Message send failed (offline)
The connection to your DataMind server was down, so the message could not go out. Wait for the connection to come back and send again; the message stays in the box.
Disconnected, reconnect now, then Reconnecting, reconnect now
The connection to your company's server dropped. Select the pill to reconnect; work resumes when the connection returns, and the pill shows Connected for a moment.
Access and permissions
You see
What it means and what to do
Your account does not have access to DataMind Oda. Ask your administrator.
Ask your administrator for Use DataMind Oda.
Your account is not allowed to run DataMind Oda in full access mode. Choose another mode or ask your administrator.
Choose another access mode, or ask for Use DataMind Oda Full Access Mode.
Minds are not available for this account., or a refusal that reads Access denied. Required permission(s): Use DataMind Oda AND Use Minds from DataMind Oda
Ask for Use Minds from DataMind Oda. View Minds is not needed.
This request names a different DataMind Oda app than the one you signed in with. Sign in again from this app., on its own or as the reason in DataMind refused access: {reason} Ask your administrator.
The sign-in this app used was made in a different DataMind Oda app: the desktop app, VS Code and Excel each sign in on their own. Sign out of this app and sign in again from it.
The DataMind Oda browser is not enabled for your account. Ask your administrator to turn it on.
Ask for Use DataMind Oda Browser. If you have it, the browser may be turned off for your company.
Your account is not allowed to share conversations. Ask your administrator.
Ask for Share DataMind Oda Chats.
Scheduled tasks are not enabled for your DataMind Oda account. Ask your administrator to turn them on.
Ask for Schedule DataMind Oda Tasks. If you have it, scheduled tasks may be turned off for your company.
DataMind Oda updates itself from your company's DataMind server. It downloads a new version in the background and installs it when your computer is idle and no task is running, or when you quit the app. It never restarts in the middle of a task without asking. To check for an update yourself, and for what to do when an update will not install, see Update DataMind Oda.
You see
What it means and what to do
Update required: Your DataMind server needs DataMind Oda {version} or later. or Your DataMind server needs a newer version of DataMind Oda.
Your company's DataMind server needs a newer version of Oda. Update from the notice with Update now, or keep working with Open DataMind in your browser; the steps are in Update DataMind Oda.
Update Check Failed with Could not check for updates. Please try again later.
The check could not reach your company's server. Choose Retry update; check your connection.
Update Failed with Could not download the update. Please try again. or Could not install the update. Please try again later.
The download or the installation failed. Choose Retry update; after a failed install Oda asks you to confirm again.
Tasks are still in progress with Restarting to update may interrupt these tasks. Continue updating?
A restart would interrupt running tasks. Stop the tasks with Stop tasks and update, or defer with Update later. If work starts during the confirmation, review it again.
Tasks could not be stopped safely. The update was not installed. Please try again later.
The running work could not be stopped, so the install was refused and your version was kept. Try again later when the workspace is quiet.
This update could not start on this computer, so it was not installed. You still have the version you had.
The new version failed its start check, so it was not installed. Oda does not offer that version again on its own; check for updates again to retry it.
DataMind Oda is still running in VS Code. Let the reply there finish, or close VS Code, then try the update again.
Oda cannot restart for the update while it is busy in VS Code.
Models
You see
What it means and what to do
Models from your DataMind server are still loading. Try again in a moment. or Could not load models from your DataMind server. Check your connection and try again.
Wait a moment and try again; if it keeps failing, check your connection, then keep the message for your administrator. The last one also appears with your server's status number.
Sign in to your DataMind server to use DataMind models.
The model list or a model request ran without a working sign-in. Sign in again with your DataMind OS account; your chats are kept.
Your DataMind server did not offer any models.
Ask your administrator to check the models offered for DataMind Oda.
This model is not available for your account.
The model is not offered to your account. Choose another model in the picker, or ask your administrator. See Model selection and defaults.
A saved model is no longer offered, so the message box stays blocked until you choose another
The model request was rejected for an authentication reason. If the model comes from a provider you configured, check its sign-in; otherwise ask your administrator.
Browser
You see
What it means and what to do
This site is blocked by your organization’s browser rules.
Your company does not allow Oda on this site. Open it in your usual browser; ask your administrator if Oda needs it.
The page could not load; reload or open it in the system browser.
Reload the page, or use Open in system browser.
Oda could not start the browser helper
The browser tool set could not connect when the chat started. Start the chat again, or ask your administrator to check the tool set; Oda does not retry by itself.
the tab is no longer available; read the tab list to choose a current one
A step was aimed at a tab that no longer exists. Let Oda read the tab list and pick a current tab; if the page is gone, open it again.
the browser helper has closed
The browser side of the tool set is gone for that page. Let Oda open the page again so the connection is remade.
Web search and page reading
You see
What it means and what to do
Platform web search error (HTTP <status>), Platform web read error (HTTP <status>), Platform page read failed: <detail> or Platform web request aborted
Try the search or the page read again; if it repeats, keep the message and contact your administrator with it.
No results found.
The search ran and came back with neither an answer nor sources; this is a result, not a failure. Ask again with different words, or ask Oda to read a page directly.
Files and uploads
You see
What it means and what to do
Files are still uploading; send after they finish
Send was held back while at least one attached file was still uploading. Wait for the uploads to finish, or remove the pending item, then send.
Upload failed; click to retry
A file's upload did not finish. Click the card to retry, or remove the item and add it again; Send stays blocked while any item is still uploading.
Session unavailable; files cannot be uploaded
The chat cannot take uploads right now. Reopen the chat, or start a new one, and add the files again.
The file has not finished uploading; re-add it and try again
The chat no longer holds the file's upload. Remove the file and add it again, wait for the upload to finish, then send.
Folders can only be added in the desktop app; add individual files in the browser
A folder was dropped where folders cannot become references. Add individual files instead, or use the desktop app.
Only PNG, JPG, WebP, and GIF images are supported
The image is not one of the four accepted formats (or its bytes do not match its declared type). Convert it to PNG, JPEG, WebP or GIF, or attach it as a regular file.
A message can include up to {count} images or Images exceed {size} in total; remove some and try again
The batch is over the image count or the total image size the deployment allows. Remove or shrink images so the batch fits, then send.
Each image must be smaller than {size} or Image resolution is too high; compress it and try again or Image sides must be at most {size}px; downscale it and try again
One image is over a per-image limit. Shrink, compress or downscale it, then add it again.
The current model does not support images; switch to a model that does
The chat's model accepts text only; the images stay in the draft. Switch the chat's model, then send again. See Chat with Oda.
/{command} does not accept attachments; remove them first
The command does not take attachments, so it was not run and your draft was kept. Remove the attachments and run the command again, or send them in a normal message.
subagent conversations do not accept file uploads
A subagent's conversation cannot receive uploaded files. Add and send the file from the main chat instead.
Previews
You see
What it means and what to do
File not found. It may have been moved or deleted.
The file is no longer at this path. Restore or locate the file, then reopen the preview.
This page exceeds the {limit} limit and cannot be read.
The file is over the preview's size limit, so it is refused rather than shortened. Open the file in its usual application.
Preview is not available for this file type yet.
The file's type has no viewer. Open the file in its usual application.
Read failed: {message} or The {name} preview is unavailable.
The preview could not read the file or start the viewer; the detail after the colon says why. Use Retry where it is offered, or switch viewers with Open with.
This PDF requires a password; password-protected previews are not supported.
The PDF is encrypted, and the preview cannot ask for or accept a password. Ask for a copy without a password, or open the file in its usual application.
The PDF rendering process could not continue. Please retry.
PDF rendering stopped on this document. Use Retry; the document is prepared again and the tab stays open.
Office previews are unavailable. Enable the document preview service on the computer running DataMind Oda.
The document preview cannot run on this computer right now. Enable the document preview service, then open the preview again.
This Office file cannot be previewed. It may be damaged, password protected, or have the wrong extension.
The file could not be read as a Word or PowerPoint document. Check it in its usual application; Retry is offered.
This spreadsheet could not be opened. Check its format, contents, or password protection.
The file could not be read as a workbook. Check it in its usual application, fix or re-export it, then use Retry.
This workbook exceeds the preview size limit.
The workbook's bytes or its combined cell area go over the preview's limits, so it is refused rather than read in part. Open a smaller or simpler workbook.
Terminal
You see
What it means and what to do
This terminal no longer exists. Open a new terminal.
The tab's shell process is gone (it ended, or Oda restarted). Use New terminal in the tab, or open one from the panel's Start page.
The terminal limit has been reached. Close unused terminals and try again. Exited terminals also count toward the limit.
The chat keeps its maximum number of terminals. Close unused terminal tabs, then open a new one.
The input buffer is full. Reconnect and try again.
Queued input was over the 64 KiB limit for one request. Press Reconnect and continue with a smaller paste.
The terminal connection ended. Reconnect to continue. or Disconnected.
The output stream ended, or the connection dropped. Press Reconnect; the terminal reattaches without restarting the shell.
The terminal screen could not be received. Reconnect to recover it.
A screen frame arrived out of order or a snapshot was missing. Press Reconnect; the current screen is restored from a snapshot.
Process exited ({code})
The shell itself exited and is not restarted automatically. Open a new terminal; the exited one counts toward the limit until you close it.
Commands and file limits
You see
What it means and what to do
[sandbox: file access denied under <mode> mode]
A step needed more access than the chat's mode allows; the change was not made. Allow the wider retry when Oda asks, change the chat's access mode, or keep the work inside the workspace folder. See Command sandboxing and approvals.
DataMind Oda can't limit writes to <folder> because no sandbox is usable on this computer. Choose a folder you own, or switch to Full access. or DataMind Oda can't limit writes to <folder> because Windows denied changing its permissions. Choose a folder you own, or switch to Full access.
The file limits cannot be applied to this folder. Allow the one unrestricted run only if it is safe, choose a folder you own, or switch the chat to Full access.
DataMind Oda can't limit writes to <folder>. Run this command without restrictions?
The approval question asked before one command runs without the file limits. Answer only if that command is safe to run unrestrained; nothing runs before your answer.
Running this command without restrictions was not approved, so it did not run.
The unrestrained run was declined. Allow it on a later try, switch to Full access, or use a folder you own.
No approval prompt is available here, so this command did not run.
Nothing could ask you, so the command was not run without limits. Use a folder you own, or Full access where it is offered.
Skills
You see
What it means and what to do
Sign in to your DataMind server to turn your organization's skills on or off.
You are signed out, or signed in to another organization. Sign in to your organization's DataMind server, then use the switch again.
Your organization has no skill named /nameto turn on or off.
Your organization removed the skill or no longer offers it to you. Open Settings > Skills again to see the current list.
Your organization requires /name, so it cannot be turned off.
Required skills stay on in every agent preset and scheduled task. Ask your administrator if you need it off.
The skills folder could not be changed: followed by a reason
Oda could not save your change on this computer. Fix what the reason names, for example a full disk or a folder you cannot write to, and try again.
Could not read all plugins, possibly due to a network problem
Oda could not read every plugin's details. Choose Retry to read them again.
Could not enable: {reason} or Could not disable: {reason}
A switch failed and the row names the reason. Repair the cause, then switch again; a failed switch changes nothing.
No registry could be reached (tried: {registries}); check the network or proxy settings, or change the registry or The plugin registry could not be reached; check the network and try again
No source answered. Check the network or proxy settings, or change the registry, and start the check again.
This is not a package name or address that can be installed: {reason}, No such plugin was found or The path does not exist or is not a valid plugin package
The address, name or folder cannot be installed. Fix it and start the check again; nothing was installed.
Other configuration still uses this bundle's components; switch them off first.
A higher-priority setting keeps the bundle's parts active, so the removal was refused. Switch off the parts that keep it active, then remove it.
Install only plugins you trust: they run with your permissions and can damage DataMind Oda or leak your data.
An installed plugin runs on this computer with your permissions. Install only plugins you trust.
Scheduled tasks and reminders
You see
What it means and what to do
Sign in required. in a run's history
The run could not sign in. Sign in to Oda again; the next run works.
The previous run was still running., Stopped by you., <n>-hour limit reached., DataMind Oda was closed during the run. or Your DataMind account does not allow Full access, so the task cannot run with Full access.
The run's history names why it did not finish; a task runs one run at a time, and the time limit or a stop ends a run early. See Schedule recurring tasks.
The computer was asleep. or The computer was asleep, and wake timers are turned off in the Windows power settings.
A run's slot passed while the computer slept. Missed slots are not caught up; keep Wake the computer to run on and check the wake timers. See Waking the computer.
DataMind Oda was closed. or DataMind Oda was closed before the run started.
Oda was not running when the slot passed. Missed slots are not caught up; the run history keeps them and the task continues at its next slot. Use Run now to start a run by hand.
The scheduled run failed: <message> or The scheduled run was stopped: <message>
A failed run always notifies, and a stopped run (for example by the time limit) does too. Open the run's chat to see the cause and the results so far.
The scheduled task could not be changed: <reason>
The save failed and the reason follows. Fix what the reason names and save again; keep the message if you contact support.
Full access and the run folder can only be changed on the task page, so the task does not run until task.json is changed back or the task is saved there.
A hand edit to the task's files tried to change Full access or the run folder. Change the files back, or open the task and save it on its page.
Models could not be loaded: <reason> or Skills could not be loaded: <reason>
The task form could not load the list. Press Retry in the field; if it keeps failing, check the connection to your DataMind server.
That saved version no longer exists. or That saved version is damaged and cannot be used.
A version of the task's files was removed or is damaged. Save the task again on its page to make a fresh version.
The session schedule log is corrupt.
The chat's reminder list could not be read. Ask Oda to list the reminders; set again anything that is missing.
The schedule operation failed.
The reminder step failed for an unexplained reason. Try the request again.
Chat turns, goals and long replies
You see
What it means and what to do
This turn failed
The turn ended with an error; the reason (and a code, when there is one) is shown with it. Choose Continue on the row to carry on in the same chat; the steps Oda finished are kept. If it repeats, keep the message and its code for your administrator.
Lost connection to the DataMind AI service, with a line such as Oda retried 25 times over about 2 minutes and could not reconnect.
The DataMind AI service dropped the connection or stopped answering, and Oda's own retries (up to 25 tries over about 2 minutes in the desktop app and VS Code, up to 5 in Excel) did not bring it back. Details holds the service's message and code. Choose Continue to carry on in the same chat; the steps Oda finished are kept. If it keeps happening, keep the code from Details for your administrator. See Failures and recovery.
Stopped or Interrupted
The turn was stopped before it finished; a tool call that was still running is kept as an interrupted result. Send a new message if you want to continue the work.
Waiting to retry model request, then Retrying model request
A model request failed and Oda is retrying on its own; the row counts down to the next attempt. Nothing to do; stopping the reply cancels the wait.
Output token limit reached
The model reached its output limit and the reply stopped part-way; the text before the cut is kept. Send continue as your next message to let the model resume, as the row's hint says.
Goal on hold with a reason such as Paused: Oda was closed. Resume to continue.
The goal stopped continuing on its own and waits for you; nothing is lost. The reason says what stopped it, for example Paused: lost connection, Stopped by you or Paused: the reply hit the output limit. Choose Resume to continue.
No activity for 25m on the goal card
Nothing has happened for at least 20 minutes while Oda was neither waiting nor running a tool. Open the chat to see where it stands; Pause the goal, or stop the reply and send a message.
Goal blocked · Time limit
The goal passed its window for automatic continuation. Choose Resume to continue; resuming restarts the window.
Goal blocked · Round limit, and Safety limit reached: 300 automatic rounds on the card
The goal used up its automatic rounds. The notice offers Edit instead of Resume; adjust the objective before continuing. See Goals.
Session logs and recovery
You see
What it means and what to do
session "<id>" uses log format v<version>, but this version of DataMind Oda reads only v<current>
The log was written by a newer version of Oda, so this version refuses to open it. Update DataMind Oda, then open the chat again. See Session upgrades.
session "<id>": stored log is corrupt: <detail> (raw log: <path>)
The stored log is damaged; the detail names the failed check, and the path is the raw file on this computer. Keep the file as it is and contact your DataMind OS administrator with this message. See Session log problems.
session "<id>" recovered from a torn tail; incomplete tail bytes were discarded
Oda found an incomplete piece at the end of a log and opened the chat with every complete record before it. Nothing to do; the recovered records are saved on Oda's next write to the chat. See Session recovery.
Subagents
You see
What it means and what to do
A run that does not complete reports a stop-reason headline and a Diagnostic: line
Open Settings > DataMind account. Log out signs you out of Oda. Change server takes you back to the Enter your DataMind URL screen; use it when your company's DataMind server moves to a new address.
Do I lose my chats when I log out?
No. Your chats stay on your computer and are there again when you sign in.
Where are my chats, settings and plugins kept?
In Oda's own folder inside your user profile on this computer; Oda does not read another installation's folder. The sign-in credential Oda saves is protected by Windows data protection, and the short-lived credential it uses while Oda runs stays in memory. Logging out keeps your chats. See Account, data and updates.
What does Oda send, and where?
Every network call goes to your company's DataMind server, and nowhere else: the sign-in, chat and model calls, web search and page reading, the company data tools, and updates. The app sends no telemetry of its own; the only reporting is your company's optional anonymous usage reporting, described in Usage reporting and the installation id.
Why did my request fail for a moment?
If your company's server restarts, requests can fail for a short time. Oda sends a failed model request again on its own, up to 25 tries over about 2 minutes in the desktop app and VS Code (up to 5 in Excel), and the turn continues when the server answers again; wait a moment. If it does not come back in that time, the chat shows Lost connection to the DataMind AI service; choose Continue to carry on once it is back. If failures continue, keep the message and contact your administrator.