Async job queue
Last updated 2026-06-14
Definition
An async job queue moves heavy work off your request so the screen never hangs waiting. When Quri has a big sync or rebuild to do, it hands the job to a queue and answers you right away. A worker picks the job up, an idempotency key stops duplicates, and a second worker adds throughput and reliability.
How to do this in Quri
- Trigger something heavy in /app, like a full source sync or a journey rebuild.
- Quri queues the job and returns control to you instead of blocking the page.
- A worker runs the job in the background; an idempotency key keeps a retry from doing it twice.
- See the result land in your views once the job finishes.
Frequently asked
- What does the idempotency key protect me from?
- Duplicate work. If a job is delivered or retried twice, the idempotency key lets the worker recognize it has already handled that exact job, so you get one clean result instead of double-counted data.
- Why run a second consumer on the queue?
- A second worker means jobs keep moving even when one is busy, and the system tolerates a worker failing without stalling the queue. You get steadier throughput and more reliable completion of heavy work.