Each time a scheduled task runs, its work happens in a new chat. This page shows where runs appear, what the history records, why a run was skipped or stopped, and when Oda notifies you. To create or change a task, see Schedule recurring tasks.
Daily report · 2026-09-25 09:00, in your computer's time. Renaming the task retitles its runs.Scheduled · <task>.{{now}} becomes the time the run starts.{{scheduledFor}} becomes the time the task was set to run.{{lastSuccessfulRun}} becomes the time of the last successful run; it is empty before the first successful run.Runs are unattended, so a few things work differently from a chat you sit in:
Question to the user: <question>. The refusal reads: No one is watching this scheduled run, so the question cannot be answered.A task starts one run at a time, and waiting runs start in the order they were queued. A slot that arrives while the previous run is still going is recorded as Skipped.
| Status | What it means |
|---|---|
| Queued | The run is waiting to start. |
| Running | The run is going now. |
| Done | The run finished, including a run that stopped at its output limit. |
| Failed | The run ended with an error; the history keeps the error's message. |
| Skipped | The slot did not start a run; the history names the reason. |
| Aborted | The run was stopped: it reached the task's time limit, or you stopped it. |
The history gives a reason for every run that did not go as planned:
The computer was asleep. The slot passed while the computer slept.The computer was asleep, and wake timers are turned off in the Windows power settings. The computer slept through the slot, and Windows does not wake it for the task.DataMind Oda was closed. Oda was not running when the slot passed.The previous run was still running. The new slot was skipped because the previous run had not finished.Sign in required. The run could not sign in to your DataMind server.Stopped by you. You stopped the run.<n>-hour limit reached. The run reached the task's time limit and was stopped.DataMind Oda was closed during the run. or DataMind Oda was closed before the run started. Oda closed while the run was going, or while it was waiting; the run is recorded as Aborted the next time Oda starts.Your DataMind account does not allow Full access, so the task cannot run with Full access. The task is set to run with Full access, but your account is not allowed to give it.Skipped slots are not caught up. When Oda comes back, a slot it reaches shortly after its time still runs, the newest missed slots are kept in the history, and nothing runs twice to catch up. Around daylight-saving changes, a local time the clock skips runs the same distance after the gap, and a time the clock repeats runs once, at its first occurrence.
For the wake setting, and how Oda wakes a sleeping computer, see Wake the computer for a scheduled run.
The scheduled run failed: <message> or The scheduled run was stopped: <message>.The scheduled run finished. only when the task has Notify when a run finishes turned on.Scheduled or Run by hand), the status, the actions the run was denied (1 denied, or None), the duration (1 h 05 min), the tokens used (compact counts such as 12K), and the run's chat.A task with no runs yet shows No runs yet. New results count as unread: the task shows 2 new, and Mark all read clears the count. Opening a run marks it read. Your start page adds a line when there are new results or something needs you, for example 2 scheduled runs finished. or 1 needs you →.
Under Scheduled in the sidebar, inside its task, or in the task page's history. Opening a run opens its chat and marks the run read. Search names run chats Scheduled · <task>.
The history row names the reason. Common ones: the computer was asleep or Oda was closed at the slot's time, the previous run had not finished, or the task asks for Full access your account does not allow. Skipped slots are not caught up.
No. When Oda comes back, a slot it reaches shortly after its time still runs, but older missed slots stay as Skipped records, and a task never runs twice to catch up.
Two causes: the run reached the task's time limit (the reason reads <n>-hour limit reached.), or you stopped it (Stopped by you.). To give long work more time, change the task's Time limit; see Schedule recurring tasks.
Yes. A running or queued run offers Stop in its history row and in the Activity feed. The history records it as Aborted, with the reason Stopped by you.
The history keeps the error's message. Two common messages: Sign in required. when Oda was signed out (sign in again, then the next run works), and the Full access sentence when your account does not allow it. If the message is unexpected, keep it and contact your administrator; Troubleshooting lists common messages.
Failed and stopped runs always notify. A run that finishes notifies only when the task has Notify when a run finishes on. Skipped runs never notify, and clicking a notification opens the run's chat.
{{now}} and {{scheduledFor}} become the run's start time and its scheduled time, in your computer's time. {{lastSuccessfulRun}} becomes the time of the last successful run, and is empty before the first successful run. Variables Oda does not know stay as written.
It has a run that failed or was stopped and you have not opened it yet, or the task itself has a problem. Open the task to look; Mark all read clears unread runs.
Runs and task folders are kept out of the usual workspace lists and pickers, so the lists keep only your own work. You always find runs under Scheduled, and search finds them named Scheduled · <task>. For the workspace lists themselves, see Browse workspace files.