Introduction
Open the Queues tab under Monitoring in any environment that uses managed queues to see how each queue is processing jobs. The dashboard shows a card for every managed queue, followed by the environment’s failed jobs. The same queue cards also appear on the environment’s Metrics tab.
The lifecycle of a job
The queue metrics follow each job through the same steps:- Your application queues the job by dispatching it.
- The job waits in the queue until a worker is free. If you dispatched it with a delay, it is delayed until the delay passes, then waits like any other job.
- A worker picks up the job and starts processing it.
- The attempt ends in one of three ways. The job is processed successfully, released back to the queue to be tried again, or permanently failed.
Live status
Next to each queue’s name, Laravel Cloud shows how many jobs are in the queue right now:
These are approximate counts at the current moment. They ignore the time range and deployment selectors. A Paused badge appears when you have paused the queue.
A Waiting count that keeps growing means jobs are arriving faster than your workers can finish them. Laravel Cloud adds workers as the backlog grows, up to the queue’s maximum. If the backlog keeps growing while the queue runs at its maximum workers, raise the maximum or make the jobs faster.
Job volume
The Job volume chart counts what happened to jobs during each interval of the selected range. Each line is a number of events, not the number of jobs in the queue at that moment:Queued is not the number of jobs sitting in the queue. It counts dispatches during each interval. To see how many jobs are waiting right now, use the Waiting count in the queue’s live status.
Duration
The Duration chart shows how long workers spent running each attempt, from the moment a worker picked up the job until the attempt finished, was released, or failed. It does not include the time the job spent waiting in the queue.- Avg: the average attempt duration during each interval.
- Peak: the longest single attempt during each interval.
Memory
The Memory chart shows the highest memory usage of any worker on the queue, as a percentage of the worker’s memory size. Hover over the chart to see the memory in use, such as45.0% (115/256 MiB). The headline Peak value is the highest percentage during the selected range.
The chart can briefly exceed 100% when a job uses more memory than its worker allows. The worker then restarts and Laravel Cloud retries the job. If the chart regularly approaches 100%, choose a larger memory size. See the queue worker memory sizing guide for help choosing one.

