Scheduled tasks
Use an existing evaluation task version as a fixed template to create and execute new Runs on a schedule. This is useful for checking the same configuration regularly.
For users who need recurring evaluations. Verification baseline: the project's current implementation as of 2026-10-30. Entry points in deployed environments may vary by version and permissions.
Search keywords: hourly, daily, weekly, monthly, time zone, schedule, next run.
1. Create a schedule
- Go to Evaluation tasks, click Scheduled task list, then click New Scheduled Task.
- Select an existing, fully configured evaluation task as the template. Agent, large language model, and preset-result tasks are all supported. Assets and configurations are validated again when the schedule is created.
- Select Hourly, Daily, Weekly, or Monthly and enter the corresponding time. For weekly schedules, select a day of the week; for monthly schedules, select a date.
- Check the browser time zone and schedule shown on the page. After creation, check the recurrence, template, status, and next run time in the list.
| Recurrence | Rule |
|---|---|
| Hourly | Runs at the start of every hour; no minute selection is available. |
| Daily | Runs at the specified time in the selected time zone. |
| Weekly | Specify a day of the week and time. |
| Monthly | Specify a date and time; dates 29—31 run on the last day of shorter months. |
For example, if the browser time zone is Asia/Shanghai, selecting daily at 09:00 runs the task on Beijing time. If your browser uses another time zone, check the page notice first rather than assuming Beijing time still applies.
2. View, edit, and delete
- Filter schedules by status in the list and check the next run time, cycle attempt count, and failure information. After a trigger, go to the regular task list to view the corresponding Run and results.
- Only schedules in Queued status allow edits to the recurrence, time, and IANA time zone. Check the next run time again after saving.
- Read the confirmation instructions before deleting. Deletion prevents future scheduled triggers, but an evaluation that has already started may still finish.
3. Fixed versions and limitations
A schedule is bound to the task version selected at creation. Each trigger produces a separate Run and run snapshot. Later edits to source assets or new task versions do not silently change existing schedules. To use a new configuration, validate it first, then recreate the schedule using the correct template.
The same template cannot have multiple active schedules at once. Only four fixed recurrence options are currently available; custom cron, holiday calendars, and dependency orchestration are not supported. A schedule's status does not represent Run quality. After a schedule triggers successfully, you still need to review the new Run's calls and scoring results.
4. Next steps and related pages
- View Runs created by scheduled triggers: Evaluation tasks.
- Analyze recurring evaluation results: View results and execution traces.
Return to the manual home page:

