frappe-syntax-scheduler

To configure Frappe scheduler_events for cron jobs, define correct scheduling patterns in your hooks.py file using standard cron syntax for precise timing. You must run bench migrate after editing scheduler_events to ensure changes are registered and applied reliably.

To prevent duplicate background jobs in Frappe v15+, implement job deduplication by assigning a unique job_id and checking it with the is_job_enqueued function. This ensures only one instance of the task runs at a time, avoiding overlapping executions.

The correct way to enqueue background jobs in Frappe is using frappe.enqueue or frappe.enqueue_doc for async processing. You must select the appropriate queue and timeout settings to ensure heavy work is delegated safely without blocking the main thread.

To handle errors and commits in Frappe scheduled functions, implement per-record commit and rollback logic within your execution loop. This isolates failures, ensuring one record error does not halt the entire job and safe database states are maintained.

Frappe supports admin-executed scheduled functions across versions 14 to 16. Configuring these functions requires careful attention to admin execution context and queue selection to ensure tasks run reliably under the correct administrative permissions.

A key limitation of Frappe scheduler_events configuration is the strict requirement to run bench migrate after edits, without which changes silently fail to apply. Additionally, older Frappe versions lack built-in job deduplication features available in v15+.