Tasks and schedules

Two kinds of tasks

• Immediate task: started from a session and executed once.
• Scheduled task: triggered on a schedule, for example a daily operations report at 09:00.

A scheduled task is a definition. Each trigger creates an instance, and the instance is what a client claims and executes.

Create a task

1. Open Tasks and choose New task.
2. Describe the goal, deliverable, and acceptance checklist.
3. Choose the execution machine (local by default) and trigger.
4. Save. Immediate tasks become claimable; scheduled tasks fire on plan.

Verification loop

A task does not become Done automatically:

1. The executor submits a result (Markdown, attachments, self-check).
2. The system creates an independent verification task.
3. A verifier on another machine or session reviews it.
4. Only a pass completes the task; a fail sends it back. After the maximum rounds, a person must take over.

The reason is simple: an executor saying it is done is not the same as the result being usable.

Run history

Task details show:

• Current status, execution machine, and start time.
• Each run and round.
• Submitted results and verification verdicts.
• Rework reasons and history.

Scheduled task notes

• A scheduled task needs an online client to claim it; it does not run while the machine is offline.
• Editing a definition does not change instances that already exist.
• Deleting a definition stops future triggers; historical instances remain.
• Time zone follows the tenant configuration, default Asia/Shanghai.

Good candidates for schedules

• Daily operations or cash reports.
• Weekly competitor monitoring and summary.
• Scheduled inspections: logs, backups, endpoints, disks.
• Recurring reconciliation and difference alerts.

Avoid fully automating high-risk actions that need human judgment; generate the result first and let a person confirm.