Job Schedule Reference #
This page provides a quick-reference table of all 8 background jobs, their run intervals, and what each one does.
What DMSI Service Management Adds
All 8 jobs are new. They do not exist in Core or WooCommerce.
Job Schedule Table #
| Job Name | Interval | What It Does |
|---|---|---|
| Hour Alerts | Every 1 hour | Checks all active contracts for hour usage exceeding 70% or 90% threshold. Queues alert emails when thresholds are crossed. |
| Overdue Checker | Every 1 hour | Identifies requests past their due_date with open status. Fires dmsi_sm_request_overdue hook and queues overdue notification emails. |
| Escalation Checker | Every 30 minutes | Evaluates defined escalation rules against open requests. Creates escalation records and queues escalation-notification emails. |
| SLA Compliance | Every 15 minutes | Checks open requests against their SLA template targets (response and resolution). Fires dmsi_sm_sla_breach hook when a breach is detected. |
| Contract Renewal | Daily | Processes auto-renew contracts (auto_renew=1). Extends end dates, handles hour rollover, queues contract-created emails for renewed contracts. |
| Asset Renewals | Daily | Checks all asset expiration dates. Queues asset-expiring-soon emails at 30-day and 7-day thresholds. |
| Maintenance Requests | Daily | Evaluates schedule-based automation triggers. Creates service requests for automations configured with a maintenance schedule. |
| Automation Runner | Every 15 minutes | Evaluates all enabled event-based and schedule-based automation rules. Executes configured actions. Logs results to the automation log. |
Interval Accuracy #
Action Scheduler intervals are approximate, not exact. A job scheduled to run every 15 minutes may run at 14 or 16 minutes depending on traffic volume and server load. For time-sensitive operations (like SLA breach detection), this means a breach may be detected up to 15 minutes after it technically occurred.