This page is machine-translated from French. Read the French original.
Planned tasks
A scheduled task automatically executes an agent's instruction according to a schedule. No one needs to be in front of the screen.
Available only in single-user mode, This typically occurs on the desktop application. On a multi-user instance, the screen disappears from the menu and tasks do not run.
What is it for?
- Daily monitoring of defined sources.
- A periodic check on a database or connected system.
- A monthly report built from a database.
A task is not attached to any workspace: it has no access to the documents or conversations of a workspace, and uses the default model of the instance.
Create a task
Settings → Agent → Planned tasks.
A task involves:
- a name;
- an instruction — exactly what you would write to an agent, but without anyone to clarify afterwards;
- the skills that the task can use; if none are chosen, it is performed without tools;
- a calendar, created with the builder or entered in cron format;
- an activation switch.
When the «Create scheduled tasks» skill is enabled, the agent can also create a task from a conversation, after your approval.
There is no limit to the number of active tasks. However, only one runs at a time by default, the others wait their turn, and each execution is interrupted after 5 minutes.
The calendar
The cron format describes a recurrence in five fields: minute, hour, day of the month, month, day of the week.
| Expression | Meaning |
|---|---|
0 7 * * 1-5 |
At 7:00 a.m., Monday to Friday |
0 8 * * 1 |
Every Monday at 8:00 AM |
0 */4 * * * |
Every four hours |
30 18 1 * * |
The 1st of each month at 6:30 PM |
The interface displays the expression in plain text and the next planned execution, allowing verification before activation.
The calendar is stored in Universal Time (UTC). The builder lets you choose a local time and performs the conversion, then the display reverts to local time. However, a manually entered expression is read in UTC: the times in the table above would be offset by one or two hours from Swiss time, depending on the season. Always check the next displayed execution.
Write a good instruction
A planned task is executed without anyone to resolve any ambiguity. It requires more precision than an interactive request.
Insufficient:
Fais un résumé de la semaine.
Correct :
Consulte les pages Actualités des trois sites suivants : [adresses].
Relève les publications des sept derniers jours.
Produis une note structurée en trois parties :
1. Publications nouvelles, avec leur date et leur source
2. Sujets qui reviennent sur plusieurs sites
3. Pages que tu n'as pas pu consulter
Si aucune publication n'a eu lieu, réponds exactement : AUCUNE ACTIVITÉ.
Enregistre la note comme fichier daté.
This instruction assumes that the task requires web reading and document creation skills.
Three rules:
- Plan for the empty case. Without explicit instructions, an agent faced with a lack of data often invents something.
- Specify the destination of the result. File, note, draft: a task whose result has no destination is useless.
- Define the perimeter. «The last seven days», «the following three sites»: without limits, the task drifts.
Monitoring of executions
Each task maintains a history: date, duration, status, and result of each execution, which can be viewed in detail along with the instructions, tool calls, generated files, and response. An execution can be started on demand, stopped, or continued within a conversation.
This is essential for:
- verify that a task is actually working — a silent task may have been failing for weeks;
- understanding failure; ;
- adjust the instruction based on what is actually produced.
Make it a habit to check the history after the first few executions. A task that is set up but never checked is a task whose status is unknown.
Points to consider
A task consumes resources each time it is executed. An hourly task at an external provider generates a continuing cost, even when it finds nothing.
A task is executed without human validation. Actions that normally require approval are automatically approved: writing a file, creating a draft, modifying a calendar. The only exception is sending, replying to, or deleting emails, which is denied because no one can approve them; the task can prepare a draft. SQL queries, MCP tools, and workflows run without approval, as is standard practice. Enable only what is strictly necessary, and prioritize skills that produce results rather than those that simply send them.
Disable what is no longer needed. A forgotten task continues to run, consume, and produce results that no one reads.
Check after making a change. A change in model, skill, or prompt can alter the behavior of a task that was working.
