convex-cron-jobs

Scheduling recurring backend tasks in Convex requires defining crons.interval or crons.cron expressions in the convex/crons.ts file. This pattern enables reliable automation for workflows like cleanup and data synchronization using UTC-based timing.

Yes, Convex supports cron expressions and fixed intervals for backend tasks like data synchronization and cleanup. The pattern library provides built-in guidance for secure internal function invocation, batching, and logging to ensure production-grade execution.

Yes, secure cron job execution in Convex requires using internal functions from the _generated API. This approach protects access and enforces proper usage, ensuring scheduled recurring tasks execute securely without exposing public endpoints.

Monitoring recurring scheduled tasks in a Convex application involves following production-grade observability best practices. This includes implementing logging within your cron jobs and processing tasks in batches to ensure predictable, reliable execution.

Convex handles scheduled cron jobs using UTC-based timing. When defining recurring tasks in convex/crons.ts, you must account for this UTC standard to ensure background jobs like reporting and monitoring execute at predictable intervals.