What is this module?

Odoo's built-in Scheduled Actions (ir.cron) run silently in the background. When they fail, degrade, or stop executing — you find out from an angry user, not from the system. Better Scheduled Actions Monitor fixes that.

Every cron execution — whether it succeeds, fails, or takes unusually long — is automatically captured in a dedicated log. A real-time health dashboard gives administrators an instant overview. Alert rules (Pro) notify your team before problems become incidents.

Features

Health Dashboard

Navigate to Cron Monitor → Dashboard for a live overview.

Execution Log

Navigate to Cron Monitor → Execution Log.

Every scheduled action run is stored with full context. The list view uses color coding: ■ red = failed, ■ green = success, ■ blue = running.

Columns

Built-in Filters

Group By

Group results by Cron Name, Status, or Execution Date for trend analysis.

Form View — Failure Details

Open any failed execution to see the full error message and Python traceback under the "Error Details" tab. Use the Re-run button to immediately re-trigger the cron.

Stat Button on Scheduled Actions

Open any Scheduled Action (Technical → Automation → Scheduled Actions) and use the Execution History smart button to jump directly to that cron's log.

Alert Rules

Navigate to Cron Monitor → Alert Rules (requires Manager role).

Alert rules define conditions that should trigger notifications. The alert engine is designed for Pro-tier extension — rules and notification records are fully CRUD-manageable from the UI.

Reports & Export

PDF Health Report

Select one or more records in the Execution Log list, then use Print → Health Report to generate a QWeb PDF showing all selected executions with cron name, status, timestamps, and duration.

CSV Export Wizard

Navigate to Cron Monitor → Export Report. Choose an optional date range and click Export CSV to download a spreadsheet with all execution data for analysis in Excel or Google Sheets.

Exported columns: Cron, Status, Start, End, Duration (s), Worker, Database, Error.

Installation

/your_addons_path/
└── cron_monitor/
    ├── __manifest__.py
    ├── models/
    ├── views/
    └── ...

python odoo-bin -c odoo.conf -u base --stop-after-init

python odoo-bin -c odoo.conf -i cron_monitor --stop-after-init

Dependencies & Compatibility

How It Works

The module inherits ir.cron and wraps two methods:

• _callback — called by the Odoo cron scheduler for every scheduled execution
• method_direct_trigger — called when a user clicks "Run Manually"

Both wrappers open a separate database cursor to write the execution record. This isolation means a rollback in the cron job's own transaction never loses the monitoring data. The try/except in the logging helpers ensures a logging failure can never crash the cron job.

ir.cron._callback / method_direct_trigger
    │
    ├─ [separate cursor] cron.monitor.execution.create(status=running)
    │
    ├─ super() → actual cron action runs
    │
    └─ [separate cursor] execution.write(status=success|failed, end_time, duration, traceback)

A composite SQL index on (cron_id, start_time) is created at install to keep log queries fast even with millions of records.

Security Model

Edition Tiers

FAQ

Does this slow down my cron jobs?

No. Logging uses a separate cursor opened outside the cron transaction. The overhead is under 5 ms per execution. If the logging itself fails, the cron job continues normally — the exception is swallowed and logged to the Odoo log file only.

What happens to old execution records?

Records accumulate until manually deleted. For high-volume cron setups, add an archive policy or create a scheduled action that deletes cron.monitor.execution records older than N days. A built-in auto-archive policy will be added in a future version.

Can I re-run a failed job?

Yes. Open the execution log record and click Re-run. This calls ir.cron.method_direct_trigger() on the linked cron, which also produces a new execution log entry.

Does it capture cron jobs that were already installed before?

Yes. The wrapper is applied to all existing ir.cron records immediately on install — no changes needed to existing crons.

Does it work with multi-company / multi-database setups?

Each database has its own execution log. The database_name field is recorded on every execution for reference. A multi-database central hub is planned for the Enterprise tier.

Upgrading

To upgrade to a new version of the module:

python odoo-bin -c odoo.conf -u cron_monitor --stop-after-init

All existing execution log records are preserved. New database columns (if any) are added automatically by Odoo's ORM migration system.