While it works, DataMind Oda can look things up in your earlier chats on this computer: what you asked, what Oda answered and what its steps did. This page covers what Oda can look through, where each lookup stops, and what its results and refusals look like; Chat with Oda covers the conversation itself, and Chat history storage and search covers how the history is kept.
Oda chooses these lookups by itself when earlier work matters, and you can also ask it to look something up in your earlier chats. It looks in five ways:
To search your chats yourself, see Search your chats.
[outside workspace boundary] for a chat above the one being read, [outside workspace subtree] for one below it, and [outside workspace] in a parent's place. Their names and contents never appear.OR, NEAR and * are ordinary characters, so a search for OR finds the word OR.Result cap reached.No prior session matches found. for a search across chats, or No prior event matches found. for a search inside one chat.live when the chat is open in this run of Oda, persisted when it was kept from an earlier one, and both words together when both hold. unavailable means it cannot be read at the moment.untitled; when the name cannot be read at all, it adds the reason, as in untitled (title unavailable: <code>).Most lookups end with results. When one cannot finish, Oda reports why in one of these lines:
session was not found: the chat Oda went to read has no record in the history on this computer. Check that the chat is still in your sidebar, then ask again.session search is disabled in this deployment: phrase searches are switched off for this installation. The other lookups still work, because they read the record directly rather than searching it. If you need searches, ask your DataMind OS administrator.session history changed while paging; retry the complete search call: the chat changed while Oda was reading it, so the search runs again from the start instead of mixing old and new parts. Ask again if it does not.cross-session search is unavailable because the caller session has no workspace: this chat has no workspace folder, so it can read only itself. Continue in a chat that belongs to a workspace folder.current-session search requires an active step boundary: Oda could not anchor a look inside the current chat to a step. Ask again in a new message, and keep the message for your administrator if it returns.session target is outside the caller workspace: the chat Oda tried to read is outside this chat's workspace folder, so Oda refuses it. Nothing is changed.session query operation failed: something else went wrong, and the full reason was kept for Oda's log files instead of the chat. Try again; if it repeats, keep the message for your administrator.A lookup also ends when you stop the turn: nothing keeps running behind it.
Only chats in the same workspace folder as the chat it is working in. The folders must match exactly: two paths that point to the same place but are written differently do not share access, and a chat with no workspace folder can look only at itself. See Workspaces, files and permissions.
A search across chats never returns the chat that is asking. When Oda searches inside the asking chat itself, the search stops before the step that is running it, so the lookup never reads the step that started it.
[outside workspace boundary] mean in a result?A chat outside the workspace appeared while Oda read a chain of chats, so Oda shows a marker in its place: [outside workspace boundary] for a chat above the one being read, [outside workspace subtree] for one below it, and [outside workspace] in a parent's place. Their names and contents never appear.
OR or *?No. Oda reads a search as literal text: quotes, OR, NEAR and * are ordinary characters, so a search for the word OR finds the word OR.
Lookups return one bounded list with no second page. When more matches exist than the limit allows, Oda keeps the strongest ones and the result ends with Result cap reached. Ask for something narrower, for example name a chat or a period, and try again.
That message is session was not found: the chat Oda went to read has no record in the history on this computer. Check that the chat is still in your sidebar and ask again; if the message returns, keep it for your administrator.
That message is session search is disabled in this deployment: phrase searches are switched off for this installation. The lookups that read a chat or an entry directly still work. If you need searches, ask your DataMind OS administrator.
The chat changed while Oda was reading it. The message, session history changed while paging; retry the complete search call, asks for the search to run again from the start rather than mixing old and new parts. Ask again if it does not happen.
untitled mean in a result?The chat's name could not be read for that hit, so Oda writes untitled in its place, with the reason when one is known, as in untitled (title unavailable: <code>). The chat's matches are still shown.
That message is cross-session search is unavailable because the caller session has no workspace: the chat has no workspace folder of its own, so it can read only itself. Continue in a chat that belongs to a workspace folder.
No. The sidebar search is yours: it finds chats by name and by what is inside them, and you open a chat from its results (Search your chats). The lookups on this page are Oda's own; they run while it works, and they stay inside its workspace.