frappe-syntax-scheduler

To prevent duplicate background job runs in Frappe, use frappe.enqueue with a unique job_id and check is_job_enqueued before scheduling. This deduplication approach ensures only one instance executes per queue, avoiding overlapping task conflicts.

Frappe scheduler events are defined in hooks.py by mapping event names like hourly, daily, or custom cron schedules to Python methods. You must run bench migrate after changing hooks to register the new scheduler event configurations.

Frappe offers multiple queues for background jobs, and heavy or long-running processing should be delegated to the long queue. Selecting the correct queue prevents blocking default tasks and keeps standard operations responsive.

Error handling for frappe.enqueue_doc requires explicit commit-or-rollback patterns to manage database state during failures. Proper handling ensures that document method retries and progress reporting remain reliable across v14-v16 workflows.

Frappe scheduler events fail to trigger after hooks changes if bench migrate is not run, as the framework requires this command to sync new scheduler configurations. Additionally, verify correct queue selection and check scheduler diagnostics logs.