$ 34.68
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 838 |
| Technical Name |
cron_monitor_recovery |
| License | LGPL-3 |
| Website | https://www.atharvasystem.com/odoo-development |
Cron Monitor
& Auto-Recovery
Enhance scheduled action management with advanced monitoring, KPI dashboards, failure alerts, and automatic recovery features.
Key
Features
KPI Dashboard
Monitor system health using advanced KPI dashboards with quick filters for running, successful, and failed tasks.
Auto-Recovery Engine
Configure automatic retries for failed jobs with exact retry limits and precise retry delays.
Email Failure Alerts
Receive real-time automated email alerts directly to configured users when crons fail or permanently stall.
Traceback Monitoring
Capture complex execution error tracebacks right in the backend logging screen for easy and swift debugging.
Real-time Running Status
Easily check and monitor which scheduled actions are currently running in real-time.
Easy Manual Reactivation
Review permanently failed jobs, adjust root causes, and reactivate the pipeline intuitively spanning custom actions.
How It
Works
KPI Dashboard Overview
DashboardView a high-level summary header showing overall statistics: Total Crons, Active jobs, currently Running Now, and Failed tasks. This provides an instant snapshot of your scheduled actions' health.
Monitor Tab Configuration
ConfigurationInside the Scheduled Action form, the new 'Monitor' tab provides all the toggles. Enable monitoring and view the latest execution status, last duration, and set a max execution time limit.
Auto-Retry Logic
RetriesConfigure how failures are handled. Set 'Max Retries' and a 'Retry Delay'. The system tracks the 'Current Retry Count' and will flag the job as 'Permanently Failed' if all attempts are exhausted.
Failure Alerts Setup
AlertsStay informed by enabling 'Alert on Failure'. You can restrict alerts to only send when a job is 'Permanently Failed', and seamlessly select which Odoo Users should receive the notification emails.
Quick Log Access
Smart ButtonA dedicated 'Logs' smart button on the Scheduled Action form gives you immediate, one-click access to the full history of executions, duration, and error traces.
Successful Execution
SuccessWhen jobs complete normally, the monitor tab updates seamlessly, indicating a 'Success' status along with the exact duration the job took to run.
Handling Failures & Errors
ErrorsWhen a job fails, the status updates to 'Failed', the retry count increments, and the complete Python traceback is captured directly in the 'LAST ERROR' field. A chatter notification is also logged.
Permanent Failure & Reactivation
ReactivationIf max retries are reached, the job is deactivated and marked 'Permanently Failed'. A clear 'Reactivate Cron' header button allows administrators to easily jumpstart the process after fixing the code.
Comprehensive Log History
LogsDive deep into the structured log history. This dedicated list view displays exactly when jobs ran, their final status ('Success' or 'Failed'), duration, and detailed error messages on failed rows.
Quick Logs in List View
List ViewA convenient 'Logs' icon is placed directly on the main Scheduled Actions list rows. Click it to instantly drill down into a specific job's execution history without opening its form.
One-Click Failed Filter
FilteringClicking the 'Failed' dashboard card instantly applies a quick filter to the list view, isolating problem crons so you can focus on resolving execution blockers immediately.
Dynamic 'Running Now' View
Real-timeSelect the 'Running Now' card to filter the list and watch which background processes are actively locking the processor, giving you true real-time visibility into the worker queues.
Advanced Standard Filters
SearchThe search view includes powerful new defaults. Use the standard dropdown menu to easily toggle between new statuses: Running, Success, Failed, and Permanently Failed.
You may
also like
Atharva System
Innovating Odoo experiences for Enterprise and Community users.
Please log in to comment on this module