Background Jobs Have Per-Queue Controls

Background jobs now have clearer per-queue controls for scheduling, concurrency, and time budgets. Long-running work such as syncs, theme generation, media processing, and cache invalidation can be tuned by queue rather than competing as one undifferentiated workload.

Why this matters during busy launch periods

When ticketing syncs, media jobs, and theme operations are all active simultaneously, a slow media import should not block a time-sensitive theme generation job. Per-queue controls make that separation possible.

No change for editors

This is an infrastructure improvement with no change to the editing experience. The outcome is a platform that handles concurrent background work more predictably, which matters most at launch and season-change peaks.