Scheduled Tasks

Introduction

Anything that repeats and is not worth manually triggering every time is a good candidate, such as:

• checking a source for new material
• triggering a recurring research or assistant turn
• delivering results to the app or a channel at a fixed time

When the scheduled task triggers an assistant turn, it can also continue by creating download, transcode, and subtitle jobs in the Resource Library.

Prerequisites

• the app is currently in Full Mode
• if onboarding is not complete yet, first finish the Welcome setup described in Install, First Launch & Updates
• you already know whether this work belongs in the main session context or in an isolated session

Features

Workflow

1. Open the Scheduled Tasks page and create a new job.
2. Fill in the Basic Info section with a name and description.
3. In Schedule, choose Every, Cron, or At.
4. In Payload, confirm whether this job is a system event or an agent turn.
5. In Delivery, decide whether the result should stay local, be announced, or be sent through Webhook.
6. After saving and enabling the job, validate it first with a low-risk schedule or a short interval.

Run State

The scheduling surface is already an operations view. In practice, you should look at:

• Overview for totals, next wake, and recent activity
• List for current job definitions and status
• Records for specific runs, stages, and errors

If the execution state of a job is unclear, check the records first, then continue troubleshooting the job configuration or runtime environment.

Assistant Turns

When Payload is set to agentTurn, and the current assistant has the related tools enabled, the scheduled task can continue by creating:

• download jobs
• transcode jobs
• subtitle translation, proofreading, and QA jobs

The actual job state, outputs, and errors are tracked in the Resource Library.
The Scheduled Tasks page keeps the wake-up, execution, and delivery records for the scheduled run itself.

Operating Guidance

• start with low-frequency, low-risk jobs
• make inputs and outputs explicit
• keep a failure delivery path where it matters
• review recent errors and consecutive failures regularly

Configuration

When creating a scheduled task, the main settings to confirm are:

Trigger

• every for interval-based runs
• cron for expression-based schedules
• at for one-off timed execution

Session

• main when the job should continue inside an existing context
• isolated when the job needs a cleaner boundary

Payload

• systemEvent for system-oriented behavior
• agentTurn to trigger an assistant turn

Assistant and Tools

If the current scheduled task needs to keep creating library jobs through the assistant, the assistant should have:

• Library query
• Library jobs

If the job only needs reminders, delivery, or lightweight checks, the tool scope can be reduced accordingly.

Delivery

• none when the result only needs to stay in records
• announce for in-app or channel delivery
• webhook for external systems