Background Processing
Understand AutoCore queue, Worker, indexing, media, notification, and scheduled-processing boundaries.
The architecture is designed for asynchronous work through Redis-backed queues and BullMQ patterns. The API can request work without keeping an interactive request open for media processing, search synchronization, email, notification, or maintenance tasks.
Registered queue families
The source names families such as media, search-index, email,
notifications, maintenance, and payment/economy or promotion-related queues.
The Admin system registry also reports cadence and job names. A registered name
is an integration contract, not proof that its processor or scheduler is enabled
in every environment.
Worker lifecycle
- A domain service emits or requests a side effect.
- The queue boundary receives an idempotent job key.
- An enabled Worker processor performs the external or derived operation.
- Success updates derived state or an audit signal.
- Failure is retained for retry, review, or a later recovery procedure.
Operational limits
The source describes retryable, observable job patterns, but current rollout flags intentionally keep some scheduled consumption disabled. This page does not promise a job’s completion, a particular retry cadence, or a production worker topology. Those are deployment and operations concerns.