impertio-studio/frappe-impl-scheduler
> Use when implementing scheduled tasks and background jobs in Frappe v14/v15/v16. Covers hooks.py scheduler_events, frappe.enqueue, queue selection, job deduplication, testing with bench execute/scheduler, monitoring via Scheduled Job Log and RQ Dashboard, error handling, long-running job patterns, email digest, data cleanup, and report processing, queue selection, job deduplication, scheduler implementation, run task automatically, background process, scheduled task not running, async task.
npx skills add https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-impl-scheduler
Workflow for implementing scheduled tasks and background jobs. For exact syntax, see frappe-syntax-scheduler.
Version: v14/v15/v16 compatible
WHAT ARE YOU BUILDING?
|
+-- Runs at fixed intervals/times?
| +-- YES --> scheduler_events (hooks.py)
| | Task receives NO arguments
| | See: Workflow 1-2
| |
| +-- NO --> Triggered by user action or code?
| +-- YES --> frappe.enqueue()
| | Pass any serializable data
| | See: Workflow 3-4
| |
| +-- NO --> Reconsider requirements
| Aspect | scheduler_events | frappe.enqueue |
|--------|------------------|----------------|
| Triggered by | Time/interval | Code execution |
| Defined in | hooks.py | Python code |
| Arguments | NONE (must be parameterless) | Any serializable data |
| Use case | Daily cleanup, hourly sync | User-triggered long task |
| Queue control | Event suffix (_long) | queue= parameter |
| Restart behavior | Runs on schedule | Lost if worker restarts |
| Need | Event Key | Queue |
|------|-----------|-------|
| Every scheduler tick | all | short (NEVER >60s) |
| Hourly (<5 min) | hourly | short |
| Hourly (5-25 min) | hourly_long | long |
| Daily (<5 min) | daily | short |
| Daily (5-25 min) | daily_long | long |
| Weekly (<5 min) | weekly | short |
| Weekly (5-25 min) | weekly_long | long |
| Monthly (<5 min) | monthly | short |
| Monthly (5-25 min) | monthly_long | long |
| Custom schedule | cron["expr"] | short |
Rule: ALWAYS use *_long suffix for tasks exceeding 5 minutes.
| Queue | Default Timeout | Use For |
|-------|-----------------|---------|
| short | 300s (5 min) | Quick operations (<1 min) |
| default | 300s (5 min) | Standard tasks (1-5 min) |
| long | 1500s (25 min) | Heavy processing (>5 min) |
Rule: ALWAYS specify queue= explicitly. NEVER rely on the default.
# myapp/tasks.py
import frappe
def daily_cleanup():
"""Daily cleanup - NO parameters allowed."""
cutoff = frappe.utils.add_days(frappe.utils.nowdate(), -30)
frappe.db.delete("Error Log", {"creation": ("<", cutoff)})
frappe.db.commit()
# hooks.py
scheduler_events = {
"daily": ["myapp.tasks.daily_cleanup"]
}
After editing hooks.py: ALWAYS run bench migrate.
# myapp/api.py
import frappe
from frappe.utils.background_jobs import is_job_enqueued
@frappe.whitelist()
def process_documents(doctype, filters):
job_id = f"process_{doctype}_{frappe.session.user}"
if is_job_enqueued(job_id):
return {"message": "Already in progress"}
frappe.enqueue(
"myapp.tasks.process_batch",
queue="long",
timeout=1800,
job_id=job_id,
enqueue_after_commit=True,
doctype=doctype,
filters=filters
)
return {"status": "queued"}
# Run the function directly (no queue involved)
bench --site mysite execute myapp.tasks.daily_cleanup
# Check scheduler status
bench --site mysite scheduler status
# Enable scheduler
bench --site mysite scheduler enable
# Trigger all pending scheduler events NOW
bench --site mysite scheduler trigger
# Run specific event type
bench --site mysite execute frappe.utils.scheduler.trigger --args "['daily']"
bench --site mysite console
>>> frappe.enqueue("myapp.tasks.my_task", queue="short", now=True)
# now=True executes synchronously for testing
1. Go to: Setup > Scheduled Job Type
2. Find: myapp.tasks.daily_cleanup
3. Verify: Frequency correct, Stopped = No
4. Click "Run Now" to trigger manually
Setup > Scheduled Job Log
- Shows every scheduler run with status
- Filter by: status (Success/Failed), creation date
- Check execution time to detect slow tasks
# Start RQ monitor (development)
bench --site mysite rq-dashboard
# Opens at http://localhost:9181
# Show background job status
bench --site mysite show-pending-jobs
bench --site mysite show-failed-jobs
def scheduler_health_check():
failed = frappe.db.count("Scheduled Job Log", {
"status": "Failed",
"creation": [">=", frappe.utils.add_to_date(None, hours=-1)]
})
if failed > 5:
frappe.sendmail(
recipients=["[email protected]"],
subject="Scheduler Alert: Many failures",
message=f"{failed} scheduler jobs failed in last hour"
)
def sync_all_orders():
orders = get_pending_orders()
success, errors = 0, 0
for order in orders:
try:
sync_to_external(order)
success += 1
except Exception as e:
errors += 1
frappe.db.rollback()
frappe.log_error(
f"Sync failed for {order}: {e}",
"Order Sync Error"
)
frappe.db.commit()
frappe.logger("sync").info(f"{success} ok, {errors} errors")
Rule: ALWAYS wrap per-record processing in try-except. NEVER let one failure stop the entire batch.
def process_batch(offset=0, batch_size=500, total=None):
if total is None:
total = frappe.db.count("Sales Invoice", {"custom_processed": 0})
records = frappe.get_all("Sales Invoice",
filters={"custom_processed": 0},
pluck="name", limit=batch_size)
if not records:
return # Done
for name in records:
process_single(name)
frappe.db.commit()
remaining = frappe.db.count("Sales Invoice", {"custom_processed": 0})
if remaining > 0:
frappe.enqueue(
"myapp.tasks.process_batch",
queue="long",
offset=offset + batch_size,
batch_size=batch_size,
total=total
)
Rule: ALWAYS split tasks >25 min into self-chaining batches.
# hooks.py
scheduler_events = {
"cron": {
"0 8 * * 1": ["myapp.newsletter.send_weekly_digest"]
}
}
See references/examples.md Example 4 for complete implementation.
scheduler_events = {
"daily_long": ["myapp.maintenance.daily_database_maintenance"]
}
See references/examples.md Example 1 for batch deletion pattern.
frappe.enqueue(
"myapp.tasks.generate_report",
queue="long",
timeout=3600,
job_id=f"report::{frappe.session.user}",
user=frappe.session.user
)
See references/workflows.md Workflow 6 for progress reporting.
bench migrate after hooks.py changes - Required to register eventsjob_id for user-triggered jobs - Prevents duplicatesenqueue_after_commit=True from document events - Ensures data exists| Aspect | v14 | v15 | v16 |
|--------|-----|-----|-----|
| Tick interval | 240s | 60s | 60s |
| Job dedup param | job_name | job_id | job_id |
| enqueue_doc() | Yes | Yes | Yes |
| Custom queues | No | Yes | Yes |
| File | Contents |
|------|----------|
| workflows.md | 8 step-by-step implementation patterns |
| decision-tree.md | Detailed decision flowcharts |
| examples.md | 5 complete working examples |
| anti-patterns.md | 14 common mistakes to avoid |
frappe-syntax-scheduler - Exact syntax reference for hooks and enqueuefrappe-errors-serverscripts - Error handling patternsfrappe-impl-hooks - Hook configuration patternsfrappe-ops-bench - Bench commands for scheduler managementfrappe-ops-performance - Performance tuning for background jobsfrappe-testing-unit - Testing scheduled task logicTake impertio-studio/frappe-impl-scheduler from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.