The extension shows a short notice when its background service stops, when it cannot find its runtime, or when something it downloaded fails. This page explains those notices and what to do. Messages from other parts of Oda are in Troubleshooting.
The extension runs Oda's background service on your computer, and the chat cannot answer until that service runs again. When it stops unexpectedly, the notice reads DataMind Oda stopped unexpectedly.
Its background service exited with code <code>.While the service is down, the chat panel points to the same steps: Choose Restart in the notification, or run "DataMind Oda: Restart Background Service".
Rarer wordings you may meet instead, each offered with the same Restart and Show Details actions:
DataMind Oda could not start its background service. The service process could not be started.DataMind Oda could not start. The service reported a fatal problem while starting.DataMind Oda lost its connection to its background service. The extension could no longer talk to the running service.DataMind Oda stopped because its background service sent an invalid message. The service sent the extension a message it could not read.DataMind Oda stopped because its background service reported no address. The service started but did not report the address the extension needs to reach it.DataMind Oda stopped. The service exited on its own, without an error code.If the service keeps stopping after a restart, keep the report from View > Output > DataMind Oda and contact your administrator with it.
The extension ships its own runtime, which the background service runs from. When the running build has none for your computer's platform, the chat cannot start and the notice reads This DataMind Oda build has no runtime for <target>.
Reinstall the extension with the build for your computer; Oda in VS Code names both builds and the steps. If a custom runtime path is set on this computer, the notice instead reads The DataMind Oda runtime set in "datamind-oda.; point the setting at an existing runtime, or clear it to use the runtime the extension ships.
The notice Your DataMind server no longer supports this version of the DataMind Oda extension. with Version <version> or later is required. means your DataMind server no longer accepts this version of the extension. Choose Update, and VS Code looks for a newer version of the extension. The notice can appear before the sign-in starts or later while you work; Sign in to Oda in VS Code covers it in the sign-in flow.
If Oda asks you to update the extension, Sign in to Oda in VS Code shows where the notice fits in the sign-in flow.
The extension downloads some tools the first time a feature needs them. A download that fails installs nothing, and the component's row in Settings > Components reports That did not work: <message>; the text after the colon names the cause, such as The <name> download does not match its checksum; it was not installed. or Downloading <url> failed: HTTP <status>.
Try the download again on the row. Components for the extension lists every failure, from a wrong size to an address that cannot be fetched, with what to check.
Inline and next-edit suggestions check with your DataMind server before they start, and they pause when the server asks them to. Inline and next-edit suggestions lists every message they can show, from a refusal by your organisation's settings to a setting VS Code would not save, with what to do.
Every sign-in message has its own answer on Sign in to Oda in VS Code: a server address that is refused, a sign-in that times out or fails, and a saved sign-in that has expired.
The extension writes to two channels. Choose View > Output and pick one:
Keep the text from a channel when you contact your administrator about a problem.
Restart starts the background service again; it does the same as DataMind Oda: Restart Background Service from the Command Palette. Show Details opens View > Output > DataMind Oda with the technical report of the failure.
Choose Restart in the notice, or run DataMind Oda: Restart Background Service from the Command Palette. If the service keeps failing, keep the report from View > Output > DataMind Oda and contact your administrator with it.
These are rarer wordings for the same trouble: the service stopped, or the extension could not talk to it. Restart is the first step for each of them; the report in View > Output > DataMind Oda names the exact case.
<target>. What is that?The platform the running build carries no runtime for. The extension has a build for 64-bit Windows and one for Windows on Arm; reinstall with the one for your computer, and Oda in VS Code names both and the steps.
That did not work: .. What do I do?The text after the colon names the cause, and the component was not installed. Try Download again on the row; Components for the extension explains each cause and what to check.
Start with Inline and next-edit suggestions: it lists every refusal and pause with what to do, including your organisation's settings and a server that asked Oda to slow down.
On Sign in to Oda in VS Code: it lists each message with what to do, from a refused server address to a sign-in that has expired.
DataMind Oda keeps failure reports and diagnostics; DataMind Oda Suggestions records what each suggestion asked for and how it ended, with the skips at the Debug level.
Yes. Cursor runs the same extension on Windows. Oda in Cursor covers setting it up there; the notices and fixes on this page apply in both editors.