Scheduled runs and history

Each time a scheduled task runs, its work happens in a new chat in the DataMind Oda desktop app. 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.

Where a run appears

• A run starts a new chat in the task's own folder. Its title is the task name and the run's time, for example Daily report · 2026-09-25 09:00, in your computer's time. Renaming the task retitles its runs.
• Run chats sit under Scheduled in the sidebar and carry a clock badge. The task lists its three most recent runs; All runs → opens the full history on the task page.
• Open a run from the sidebar, from the run's history row, or from a notification. Opening the chat marks the run read.
• A fork of a run's chat is an ordinary chat.
• Task folders and their runs stay out of your workspace lists and folder pickers while the task exists, so the lists keep only your own work (Browse workspace files). Search still finds a run's chat, named Scheduled · <task>.
• A run you pinned stays pinned. After you delete a task, its run chats become ordinary archived chats; Show archived lists them again (Your chats in the sidebar).

The Scheduled section in the sidebar

• The section header reads SCHEDULED and shows how many tasks you have. The section can be folded, and Oda remembers your choice. When the sidebar itself is folded to its rail, a clock button stands in for the section and shows a dot while results are unread; clicking it brings the sidebar back.
• Every task is a folder that lists its last three runs. Clicking the task row opens the task page; the chevron only shows or hides the runs.
• Beside a task name you see its state at a glance: the next run, such as 09:00, Mon 09:00 or 6 Oct; Paused when the schedule is paused; Queued while a run waits its turn; and a live timer while a run is going, such as 03:12.
• A task with a problem carries a Needs attention mark. Resting the pointer on the row shows a small card with its schedule, its state, its next run and the problem text.
• Each run row shows its status and the day and time it happened, such as Today · 09:00, Yesterday · 09:00 or Mon 29 Sep · 09:00.
• If the list cannot be read, the section shows Scheduled tasks could not be loaded: {reason} with Retry.
• With no tasks yet, the section keeps just its header; New scheduled task and Open Scheduled page stay visible, and otherwise they appear when you rest the pointer on the header.
• A task that has a run going or results you have not read yet opens its runs once when Oda starts; outside that, tasks stay open or closed as you leave them.

Run and manage a task from its row

• Resting the pointer on a task, or moving focus to it, reveals Run now, Pause or Resume, and the row menu.
• Run now starts a run at once. It is unavailable while a run of the task is going, or while the task has a problem.
• Pause stops the schedule and Resume starts it again; both turn unavailable while the task has a problem. A Manual task has neither and runs only when you press Run now.
• The menu holds Edit, Mark all read and Delete. Mark all read becomes available once the task has results you have not opened; Delete asks for confirmation first.
• With the list focused, ↑ and ↓ move between tasks, Home and End jump to the first or last one, → opens a task or steps into its runs, ← closes a task or steps back out, and Enter opens the focused row.

How a run starts

• The run works on the task's preset and model, with the task's Access and skills, in the task's folder.
• Your prompt becomes the first message of the run's chat, with three variables filled in first, using your computer's time:
  • {{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.
• Variables Oda does not know are left as you wrote them.

While no one is watching

Runs are unattended, so a few things work differently from a chat you sit in:

• Steps that need approval are never approved. They are denied automatically and listed on the run, so you can see what was skipped.
• A run cannot ask you a question. The question is refused, and the run records it instead as Question to the user: <question>. The refusal reads: No one is watching this scheduled run, so the question cannot be answered. Decide yourself, or list the open question in your summary.
• A run cannot create or change scheduled tasks. Its task-management tools are hidden, apart from listing tasks; only you change tasks, from the task page or the main chat.

Run statuses

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.

Why a run was skipped or stopped

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.
• Any other reason keeps its own text.

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.

Notifications

• Failed and stopped runs always send a notification: The scheduled run failed: <message> or The scheduled run was stopped: <message>.
• A run that finishes sends The scheduled run finished. only when the task has Notify when a run finishes turned on.
• Skipped runs never notify.
• Clicking a notification opens the run's chat and marks the run read.

Read and clear new results

• A run you have not opened marks its task: the row turns bold with a dot and counts the new results, such as 2 new.
• Opening a run's chat marks that run read. If a run has no chat to open, its row opens the task page instead.
• Mark all read on the task's menu, or on the task page, clears every unread result on it at once.
• Under the greeting on your start page, a line reports scheduled results you have not opened, such as 1 scheduled run finished. or 2 scheduled runs finished. When a run failed or was stopped and you have not seen it, or when a task has a problem, the line adds a needs-you part, such as 1 needs you →; clicking it opens the first task that needs attention. With everything read, the line does not appear.

Runs in the Activity panel

• The Activity panel carries a Scheduled · across Oda band: the runs that are going or waiting across all of your tasks. Open opens a run, and Stop stops it.
• The next run due appears as one line, Next: <task> · <time>; opening it opens that task.
• These runs belong to no single chat, so they never add to a chat's counts. See Activity for the panel and its other bands.

Reading the run history

1. Open the task: click it under Scheduled, or use All runs → on its runs.
2. Find the run in the history. Each row shows the time and its trigger (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.
3. Choose Open to read the run's chat, or Stop to stop a run that is going or queued. A Skipped row offers Run now while the task has no active run.

A task with no runs yet shows No runs yet.

Questions, answered

Where do I find the chat a run created?

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>; they stay out of your workspace lists and folder pickers.

What do the times and words on a task row mean?

The next run appears as 09:00, Mon 09:00 or 6 Oct. Paused means the schedule is paused; Queued means one of its runs is waiting; 2 new counts results you have not opened; and a run in progress shows a live timer such as 03:12. Needs attention means the task itself has a problem; rest the pointer on the row to read it.

Why was my run skipped?

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.

Are missed runs caught up later?

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.

Why did my run stop before it finished?

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.

Can I stop a run myself?

Yes. A running or queued run offers Stop in its history row and in the Scheduled · across Oda band of the Activity panel. The history records it as Aborted, with the reason Stopped by you.

Why did my run fail?

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.

Which runs send a notification?

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.

What do the prompt variables become when a run starts?

{{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.

Why does one task have no Pause button?

A Manual task runs only when you press Run now, so it has no schedule to pause. On other tasks, Pause or Resume turns unavailable while the task has a problem.

What happens to a run's chat after I delete its task?

The chat stays. It becomes an ordinary archived chat that Show archived lists again. A run you pinned stays pinned.

Why does the Scheduled section show an error instead of my tasks?

Oda could not read your task list; the message names the reason. Press Retry to load the list again.