Scheduling Automations

Configure cron-based scheduling for evaluations, playbooks, crawlers, and cleanup tasks

Overview

OpenRails supports cron-based scheduling for automated recurring tasks. You can schedule evaluation runs, playbook executions, web crawler runs, and data lake cleanup tasks to run on defined intervals without manual intervention.

Cron Expression Syntax

OpenRails uses standard 5-field cron expressions:

Field Values Description
Minute 0-59 Minute of the hour
Hour 0-23 Hour of the day (24-hour format)
Day of Month 1-31 Day of the month
Month 1-12 Month of the year
Day of Week 0-6 (SUN-SAT) Day of the week

Common Examples

Expression Schedule
0 9 * * MON-FRI Every weekday at 9:00 AM
0 */6 * * * Every 6 hours
30 2 * * SUN Every Sunday at 2:30 AM
0 0 1 * * First day of every month at midnight
*/15 * * * * Every 15 minutes

Schedulable Tasks

Evaluation Runs

Schedule evaluation projects to run automatically, testing your bots and agents on a regular cadence. Navigate to Evaluations > Settings > Schedule to configure.

Playbook Execution

Schedule playbooks to run sequential agent workflows automatically. Configure from Agents > Playbooks > Schedule.

Web Crawler Runs

Schedule web crawlers to periodically re-crawl websites and update data lake content. Configure from Tools > Web Crawlers > Schedule.

Data Lake Cleanup

Schedule automated cleanup tasks to remove stale documents, rebuild indexes, or re-process content. Configure from Data Lakes > Settings > Scheduling.

Managing Schedules

View Active Schedules

Navigate to Settings > Schedules for a consolidated view of all active schedules across your project.

Enable or Disable

Toggle any schedule on or off without deleting the configuration. Disabled schedules retain their settings for easy re-activation.

Review Run History

Each scheduled task maintains a run history showing execution time, duration, success/failure status, and output summaries.

Tip: Stagger scheduled tasks to avoid resource contention. If you have multiple evaluations and crawlers, schedule them at different times to distribute the processing load.
Important: Scheduled tasks run unattended. Ensure all agents in scheduled playbooks have appropriate budget limits. Review run history regularly to catch failures early.

Next Steps