Docs / RivetMSP / Deploying & administering
Cron Manager
Enable background jobs, pick a schedule from the web, and see what runs.
Much of RivetMSP happens in the background: recurring tickets and invoices, ticket automation, RMM sync, mail delivery, scheduled reports and more. All of it is driven by cron. The Cron Manager lets you control that schedule from the web, without touching the server.
Find it under Administration > Cron.
Enabling cron#
Two things have to be true:
- A system cron entry runs the application's cron script on a regular basis. The install script adds this for you, firing every five minutes.
- Enable Cron is switched on in the application's settings. It defaults to off, and until you turn it on the script does nothing at all.
If recurring tickets, automation rules or RMM alerts seem to do nothing, check the second one first.
What the Cron Manager does#
- Shows the current schedule of the main cron job.
- Lets you change it with presets: every 5 minutes, every 15 minutes, every 30 minutes, hourly, or a custom cron expression.
- Has a Run Now button to run the job immediately.
- Shows the last successful run, so you can see at a glance that background work is happening.
- Lists the other scheduled jobs on the server.
What runs#
The main job is a dispatcher. On each run it handles recurring tickets, invoices and expenses, backups, ticket automation rules, and RMM sync with automatic ticketing. Other jobs are separate scripts, most of them also started from the dispatcher:
| Job | Purpose |
|---|---|
| Mail queue | Delivers outbound email |
| Ticket email parser | Reads mailboxes and turns email into tickets |
| Accounting sync | Pushes data to QuickBooks Online |
| CRM reminders | Sends due activity reminders |
| Certificate refresher | Refreshes SSL certificate monitoring |
| Domain refresher | Refreshes domain expiry monitoring |
| Metrics rollup | Takes a daily snapshot of ticket-flow metrics for dashboards |
| Outlook schedule sync | The pull direction of Outlook calendar sync |
| Report scheduler | Sends scheduled report emails |
UniFi needs its own cron entry#
The UniFi sync runs from a standalone script, scripts/unifi_sync_cli.php, and is not started by the main dispatcher. If you use the UniFi integration, add a separate cron entry for it.
Choosing a frequency#
Every 5 to 15 minutes suits most MSPs: automation rules and email-to-ticket stay timely. Hourly is fine for a small install. Remember that the schedule you pick is also how often automation rules are evaluated, so tickets are only acted on that often.