Loading the documentation…
A scheduled task lets DataMind Oda run a prompt on its own at the time you set, for example a report every weekday morning. Each run starts a new chat, which you find under Scheduled in the sidebar; Scheduled runs and history covers what a run does, and Where scheduled runs appear covers the results it leaves.
Scheduled tasks belong to the DataMind Oda desktop app and need the Schedule DataMind Oda Tasks permission, which your administrator turns on for the company and for your account (Manage DataMind Oda for your company). For reminders inside a chat you are working in, see Reminders.
Under Scheduled in the sidebar, click New scheduled task. When no tasks are saved yet, the section offers Open Scheduled page instead.
Fill in the task:
| Field | What to enter |
|---|---|
| Name | A name you recognise, 1 to 80 characters, for example Daily sales report. |
| Prompt | What each run should do, written the way you would ask in a chat. Each run starts a new conversation with this message. {{lastSuccessfulRun}}, {{now}} and {{scheduledFor}} are replaced with the run's times, and {{lastSuccessfulRun}} is empty before the first successful run. The prompt holds up to 100000 characters. |
| Frequency | Manual, Daily, Weekdays, Weekly or Monthly. Manual runs only when you click Run now. For Weekly, choose the Day of the week (Monday by default); for Monthly, the Day of the month (1 to 31; shorter months run on their last day). The task shows its schedule as text, such as Daily at 09:00; a Manual task reads Only when run by hand. |
| Time | The time it runs, as a 24-hour time such as 09:00, in this computer's time zone. |
| Preset, Model | How the run works: Standard mode works with code, files and information; Relentless works until done, blocked, or a real decision is needed; PTC mode is for tasks that call tools in batches; Minimal mode runs only a terminal tool; Creator mode customises DataMind through conversation (Choose a mode for a new task). The Model starts on The preset's model unless you pick another; a model you picked that is no longer offered shows as (not available). |
| Access | Workspace: the run changes files only in its folder, and anything that needs approval is denied and listed in the run history. Full access: the run works with your full rights (This task will run unattended with your full rights.); offered only when your account allows it, otherwise the field shows Your DataMind account does not allow Full access. |
| Skills | All uses every skill; Only selected and All except let you choose names from the preset's skills. A skill that is no longer installed stays listed as Not installed. Skills marked Required by your organization are available to every run, whatever skills the task selects. |
| Folder | Where the task works: The task's own folder, or a folder you choose with Choose… (Scheduled task files and versions). |
| Time limit | For long runs: the run is stopped after this many hours. The default is 5 hours, and the field's hint shows the most allowed: A run is stopped after this many hours, at most {max}. |
| Wake the computer to run | On by default on Windows: Oda wakes a sleeping computer shortly before the run, while it is plugged in (Wake the computer for a scheduled run). |
| Notify when a run finishes | Off by default. Failed and stopped runs always notify (Scheduled runs and history). |
| Paused | Create the task paused; it keeps its settings and starts running when you resume it. |
Click Create task. The task appears under Scheduled and shows when it next runs.
The form opens on these defaults: Daily at 09:00, the preset your app defaults to (Standard mode until another default is set), Workspace access, all skills, Wake the computer to run on, Notify when a run finishes off, and a 5-hour Time limit. Change any of this before or after creating the task. If the model or skill list cannot be loaded, the field says why (Models could not be loaded: <reason>, Skills could not be loaded: <reason>) with Retry; a preset with no skills says This preset has no skills.
Open the task by clicking it under Scheduled. Its page holds the same fields as the form, so you can change anything and save it.
Paused; Run now still works, so you can still run it by hand; a task with no next run shows No run is scheduled, and otherwise the page shows Next run <time>.This computer cannot open folders from the app.Delete the scheduled task "<name>"?. Deleting stops a run that is going and removes the task's settings, saved versions and run history; the chats its runs created stay (Scheduled task files and versions).A save is refused when the preset a task uses is no longer installed, or its folder is gone: The preset "<name>" is not installed. or The folder <folder> does not exist. If a save fails for another reason, the message it shows is kept under the form, such as The scheduled task could not be changed: <reason>.
In a chat, Oda can list, create, change, pause, resume and delete your scheduled tasks. Each action shows a card, for example List scheduled tasks, Create scheduled task …, Change scheduled task, Pause scheduled task, Resume scheduled task or Delete scheduled task ….
Create scheduled tasks from a chat covers the cards, the approval and the refusals in full.
Every saved change is a version of the task, listed on its page; the newest carries Current. A version records where it came from: Saved on this page, Changed in a conversation, Edited in the task folder or Restored. View shows a version's prompt, and Restore makes it the task's settings again.
Each task keeps its own folder on the computer, holding its settings (task.), its prompt (prompt.), its run history and its saved versions. You can edit the settings and prompt files by hand, and an edit takes effect at once. One exception: an edit that changes Full access or the run folder is refused, the task shows a problem, and it does not run until the file is changed back or the task is saved on its page: Full access and the run folder can only be changed on the task page, so the task does not run until task.
Scheduled task files and versions covers the folder layout, hand edits and restoring in full.
Yes. Tasks run on your computer, with Oda running. If the computer is asleep, a task with Wake the computer to run turned on still runs: Windows wakes the computer shortly before the run, while the computer is plugged in and wake timers are on (Wake the computer for a scheduled run). A computer that is shut down does not start for a task, and a missed slot is recorded as skipped (Scheduled runs and history).
No one is watching a run, so a step that needs your approval is denied automatically and listed on the run, and the run carries on with the rest. To avoid this, let the task save its files in its Folder, or choose Full access for the task (Scheduled runs and history).
Yes. Ask in the chat, for example Schedule a report every weekday at 09:00, and Oda prepares the task and shows what it will save. Accept the approval and the task appears under Scheduled. If that chat runs with Full access, Oda saves the change without asking. Create scheduled tasks from a chat covers the cards and the approval.
The Schedule DataMind Oda Tasks permission, which your administrator turns on for the company and for your account. If it is not enabled for you, Oda says Scheduled tasks are not enabled for your DataMind Oda account. (Manage DataMind Oda for your company).
A save is refused when a value breaks a rule, and the message names the rule: The task name must have 1 to 80 characters., The prompt must not be empty., The prompt must have at most 100000 characters., The time must be a 24-hour time such as 09:00., The folder must be an absolute path., The run time limit must be a whole number of hours from 1 to <max>., Choose at least one skill, or allow all skills. or Choose a preset.. Fix the value and save again.
Yes. Run now on the task page or its sidebar row starts a run at once, including for a paused task or a Manual task, which runs only this way. Run now is unavailable while a run is going, or while the task has a problem.
The model the task's preset supplies, shown as The preset's model, unless you choose another model for the task. A model you chose that is no longer offered stays on the task as (not available) until you pick another model or go back to the preset's model.
The computer's time zone. A task runs at the same local clock time, and it moves with the computer: if you change the computer's time zone, the task follows it.
The run follows the local clock. When the clocks jump forward and the task's time is skipped that day, the run happens the same distance after the change: a task set for 02:30 runs at 03:30 on that day. When the clocks go back and the same time happens twice, the run uses the earlier of the two.
No. Scheduled tasks are part of the DataMind Oda desktop app, so the Scheduled section does not appear in the browser interface.
Yes, different tasks can run at the same time, up to the limit your app allows. One task runs a single run at a time; a slot that arrives while its previous run is still going is skipped and recorded in the history (Scheduled runs and history).