Events, Queues & Cron
A simple explanation of OpenCart events, HuntBee queues and Suite schedulers for SEO and Tracking.
Understand three simple ideas used across HuntBee Suites: events, queues and scheduled workers.
1. Event = doorbell
An OpenCart event tells HuntBee that something happened. A product was saved, a cart item changed, checkout moved forward, or an order status changed. HuntBee listens only to the events required by installed Suites.
2. Queue = to-do list
Some work should not make a customer or administrator wait for an external service. The Suite records the work first, finishes the page quickly, and lets a background worker deliver it later.
SEO examples: IndexNow or AI/background jobs. Tracking examples: Meta/TikTok/Pinterest supported server events and GA4 server-side refunds.
3. Cron / scheduler = alarm clock
Your server calls HuntBee on a schedule. The Suite checks which jobs are enabled and due. Browser tracking does not wait for Tracking cron; only background/server work needs the scheduler.
SEO and Tracking use separate Suite schedules
| Suite | What its scheduler handles |
|---|---|
| SEO Suite | Enabled SEO background jobs such as queues/automation managed by SEO Cron Manager. |
| Tracking Suite | Server Event Delivery plus Queue & Log Cleanup. |
Recommended frequency
Calling the central Suite scheduler every minute is a practical default when queued work is enabled. Each Suite still decides which internal job is actually due, so a one-minute external call does not mean every job runs every minute.