convex-cron-jobs

You can schedule recurring background jobs in Convex by calling crons.interval with a descriptive name, a schedule specification, a target internal function, and optional arguments, then exporting the configured cron.

Interval scheduling executes tasks at fixed time periods, whereas cron expressions allow precise UTC timing for complex recurring schedules. Both validate via crons.interval and crons.cron to automate Convex background tasks.

Yes, you can use cron expressions for data synchronization, cleanup jobs, periodic reporting, and health checks across Convex apps. The system validates scheduling via crons.cron and enforces UTC timing for these recurring tasks.

Yes, Convex cron scheduling supports automatic retries, monitoring, batching, logging, and error handling. It calls internal functions for security while executing recurring background tasks like periodic maintenance and data synchronization.

Convex cron jobs require an internal function to enforce security. By targeting internal functions, the scheduling system ensures that recurring tasks like cleanup jobs and data sync execute securely without exposing public endpoints.