Queue configuration in Laravel - Step-by-Step Execution

Concept Flow - Queue configuration

Start

↓

Set queue driver in .env

↓

Configure queue connections in config/queue.php

↓

Run queue worker to process jobs

↓

Jobs pushed to queue

↓

Worker picks job and executes

↓

Job completed or failed

↓

End

This flow shows how Laravel reads queue settings, runs workers, and processes jobs step-by-step.

Execution Sample

Laravel

QUEUE_CONNECTION=database

// config/queue.php
'default' => env('QUEUE_CONNECTION', 'sync'),

// Run worker
php artisan queue:work

This code sets the queue driver to database, configures it, and runs the worker to process queued jobs.

Execution Table

Step	Action	Configuration State	Worker State	Job Queue State
1	Read .env QUEUE_CONNECTION	QUEUE_CONNECTION=database	Idle	Empty
2	Load config/queue.php default driver	default=database	Idle	Empty
3	Push job to queue	default=database	Idle	Job1 added
4	Start queue worker	default=database	Running	Job1 in queue
5	Worker picks Job1	default=database	Processing Job1	Job1 removed
6	Job1 executed successfully	default=database	Idle	Empty
7	Push another job	default=database	Idle	Job2 added
8	Worker picks Job2	default=database	Processing Job2	Job2 removed
9	Job2 failed, moved to failed_jobs table	default=database	Idle	Empty

💡 No more jobs in queue, worker waits for new jobs.

Variable Tracker

Variable	Start	After Step 3	After Step 5	After Step 6	After Step 7	After Step 8	After Step 9
QUEUE_CONNECTION	null	database	database	database	database	database	database
Worker State	Idle	Idle	Processing Job1	Idle	Idle	Processing Job2	Idle
Job Queue	Empty	Job1 added	Job1 removed	Empty	Job2 added	Job2 removed	Empty
Failed Jobs Table	Empty	Empty	Empty	Empty	Empty	Empty	Job2 recorded

Key Moments - 3 Insights

Why does the worker stay idle after finishing a job?

Because the queue is empty after the job is processed, so the worker waits for new jobs as shown in steps 6 and 9.

What happens if a job fails during processing?

The job is moved to the failed_jobs table for later review, as seen in step 9 of the execution table.

How does Laravel know which queue driver to use?

It reads the QUEUE_CONNECTION value from the .env file and loads that setting in config/queue.php, shown in steps 1 and 2.

Visual Quiz - 3 Questions

Look at the execution table, what is the worker state at step 5?

A Processing Job1

B Idle

C Running but not processing

D Failed

💡 Hint

Check the 'Worker State' column at step 5 in the execution table.

At which step does the job get removed from the queue?

A Step 3

B Step 5

C Step 7

D Step 9

💡 Hint

Look at the 'Job Queue State' column where the job disappears after being picked.

If QUEUE_CONNECTION was set to 'sync', how would the worker state change?

A Jobs would fail automatically

B Worker would stay idle forever

C Worker would process jobs immediately without queueing

D Jobs would be stored in failed_jobs table

💡 Hint

Recall that 'sync' runs jobs immediately, no separate worker needed.

Concept Snapshot

Laravel Queue Configuration:
- Set QUEUE_CONNECTION in .env (e.g., database, redis, sync)
- Configure connections in config/queue.php
- Push jobs to queue via dispatch()
- Run worker with 'php artisan queue:work'
- Worker processes jobs asynchronously
- Failed jobs stored in failed_jobs table

Full Transcript

This visual execution trace shows how Laravel configures and runs queues. First, Laravel reads the QUEUE_CONNECTION setting from the .env file, which determines the queue driver like database or sync. Then it loads the configuration from config/queue.php. When a job is dispatched, it is added to the queue. The queue worker runs and picks jobs from the queue to process them. After processing, the job is removed from the queue. If a job fails, it is recorded in the failed_jobs table. The worker stays idle when no jobs are available, waiting for new jobs. If the driver is 'sync', jobs run immediately without queueing. This step-by-step flow helps beginners understand how Laravel queues work internally.