cronlisted

# Cron — Scheduled Tasks & Recurring Job Orchestration ## Activate When - User invokes `/godmode:cron` - User says "schedule a job", "cron job", "recurring task", "run every hour" - User says "background scheduler", "periodic task", "timed execution" - User says "node-cron", "BullMQ repeat", "Celery beat", "Sidekiq-cron", "APScheduler", "Hangfire", "Quartz" - User needs a task to fire on a schedule (daily reports, cleanup, syncs, heartbeats) - User asks about cron syntax, timezone handling, or overlap protection - User needs distributed scheduling across multiple instances - User needs rate-limited or priority-aware recurring execution - Godmode orchestrator detects hardcoded `setInterval` or `setTimeout` loops that need conversion to proper scheduled jobs ## Workflow ### Step 1: Scheduling Requirements Assessment Evaluate what needs to run, how often, and under what constraints: ``` SCHEDULING REQUIREMENTS ASSESSMENT: | Dimension | Value | | Task type | <cleanup | report | sync | alert | | | billing | digest | health check> | | Frequency | <seconds | minutes | hourly | | ``` #### Cron Expression Quick Reference ``` CRON EXPRESSION SYNTAX: | Field | Values | Special chars | | Minute | 0-59 | * , - / | | Hour | 0-23 | * , - / | | Day of month | 1-31 | * , - / ? L W