While DataMind Oda works, some steps only manage the work itself: setting up a goal, scheduling a task, checking background work, passing a message to a teammate. Each of those steps leaves a small record row in the chat. This page explains what the rows show and how to read them.
A record row is a step row like any other: it appears in the chat with a one-line summary of what happened, and its details open in place.
Expand a row by clicking it, or by focusing it and pressing Enter or Space. Inside, you find the recorded details: labelled fields, statuses, and lists with their counts. A long list scrolls inside the expanded row.
Where the record contains text or code, a copy control puts it on your clipboard.
How step rows behave in general, including what a running or failed row shows, is covered in Oda's steps and tool results.
When Oda sets, shows or updates a goal, the chat keeps a record of it. Expanded, the record shows the goal's objective, its status, and how many rounds it has run against its limit, for example Status: Awaiting continuation and Rounds: 2 / 8.
The goal itself, its pill and the / command are covered in Chat with Oda.
Creating, listing or deleting a scheduled task leaves a record in the chat.
Scheduling tasks themselves is covered in Schedule recurring tasks.
Steps that manage teammates and background work leave short receipts: a line that says what was asked for and what came back.
Following teammates and background work as it happens is covered in The Team panel in Activity and Terminal sessions.
Longer work and lookups also leave records:
Oda lays out a record only when the saved result matches a form it recognises. When a result is partial or unexpected, or the step failed, the row keeps the plain recorded text instead, so nothing is presented as applied when it was not.
No. Each row keeps the state recorded at the moment the step ran. It is not a live view.
Your computer's. Dates appear as full dates, and they stay readable regardless of the app's language.
Because the check found no goal for the chat at that moment. To set or change a goal, use /, as described in Chat with Oda.
It is how the task repeats. Repeat: Once means a single run. An interval such as Repeat: Every 1 h means the task runs again on that interval, spelled out in whole units of days, hours, minutes or seconds.
Its scheduled time passed before the run could happen, and the task is kept as overdue rather than dropped.
By the time Oda checked, the job had already finished. There was nothing left to stop.
The message was accepted but has not reached its target yet. When it is delivered, the receipt reads Message delivered.
It records that Oda asked for the work to stop. The receipt confirms the request; it does not record what happened afterwards.
It records that a wait on a teammate ended by running out. If you still need news from that teammate, ask Oda to check again.
Oda lays out a record only when the saved result matches a form it recognises. A partial, failed or unexpected result keeps the plain recorded text, so nothing is shown as applied when it was not.