Automation

Automation is opt-in and runs on the server. Choose projects, set parallelism from 1–32, choose a schedule and save.

Schedules

Presets cover every minute, every 5, 15 or 30 minutes, hourly, daily at 09:00 UTC and weekdays at 09:00 UTC. Advanced editing accepts numeric five-field cron expressions with wildcards, lists, ranges and steps.

Schedules use UTC. Local time zones, daylight-saving adjustments, named weekdays, seconds and cron macros are unsupported. When both day-of-month and weekday are restricted, either can match.

The server records a scheduled minute before dispatching work. Restarting does not replay that minute, and downtime does not trigger catch-up bursts.

Queue order

Move eligible tasks to set their order. Queue changes save immediately. Unranked tasks use creation time for ordering, and newly created tasks append after the reordered queue. Deleted tasks, started tasks and tasks in deselected projects are excluded.

Capacity and failures

Capacity includes starting, running and queued agents, plus pending delivery, including manual runs. Agents waiting for your input do not occupy a slot. Slots refill on the next matching schedule.

Manual runs remain available above the automation limit. Pausing automation or lowering capacity does not cancel agents already running.

If a start fails, automation pauses and shows the failed task and error. Correct the issue and explicitly save to resume. Failed linked sessions require manual retry.

Server lifetime

Automation runs only while the server is running. Maintenance blocks automated dispatch without changing the saved schedule. Run one server per data directory; see server setup for services and maintenance.