Cron Settings controls how often Mumara's automated background tasks run. Your server's cron calls Mumara's scheduler every minute, and the scheduler then executes each task at the interval you configure under Settings → Cron Settings.
Each job has its own configurable frequency and can also be run manually with Run Now, or with Run Forcefully to bypass a lock (available on jobs like Bounce Processing and Maintenance Work that can get stuck). Key jobs include:
Email Campaigns (default 1 min) — starts scheduled broadcasts and processes sending queues
Trigger Processing (1 min) — runs delayed and segment-based triggers; instant triggers fire in real time without cron
Bounce Processing (2 hours) and Feedback Loop Processing (24 hours) — fetch bounces and spam complaints
Open/Click Tracking and Pending Stats (1 min) — turn raw tracking events into statistics
Maintenance Work, Segments Recount, Limit Reset (24 hours) — cleanup, recounts, and quota resets
Plus Suppression Processing, Queue Work, Stuck Campaigns, Evergreen Campaigns, and RSS content updates
Worth knowing: the defaults suit most installations — increase frequency for high sending volumes and reduce it for low-volume systems to save server resources. Use Run Forcefully sparingly: a locked job is usually still running, and forcing a second run can cause duplicate processing. None of this works unless the server-level cron entry that runs Mumara's scheduler every minute is in place.
