Cron Jobs

GridWork HQ includes 12 automated cron jobs managed by the pipeline server's built-in scheduler. All scheduling is handled internally — no system crontab is needed.

How It Works

The cron-scheduler.ts module reads cron-config.json on startup and registers each job. When a cron fires:

1. Checks if the job is already running (prevents overlap)
2. Checks quiet hours — silently skips if within the quiet window
3. Executes the job (spawns a Claude session or runs a shell command)
4. Records the result in history (success/failure, duration, output path)
5. Persists the timestamp to cron_jobs.json

History is kept in cron-history.json (max 200 entries).

Managing Jobs

• Enable/disable from the Cron Dashboard or by editing cron-config.json
• Manual trigger from the dashboard or via API
• View history in the Cron Dashboard

Restart the pipeline server after editing cron-config.json.

Guides

• Cron Configuration — Complete reference for all 12 jobs and the config format