Dispatching jobs in Laravel - Step-by-Step Execution

Concept Flow - Dispatching jobs

Create Job Class

↓

Instantiate Job with Data

↓

Dispatch Job

↓

Job Added to Queue

↓

Queue Worker Picks Job

↓

Job Executes

↓

Job Completes or Fails

This flow shows how a job is created, dispatched to a queue, picked up by a worker, and then executed.

Execution Sample

Laravel

use App\Jobs\SendEmail;

$emailJob = new SendEmail($user);
dispatch($emailJob);

This code creates a SendEmail job with user data and dispatches it to the queue.

Execution Table

Step	Action	Evaluation	Result
1	Create SendEmail job instance	new SendEmail($user)	Job object with user data created
2	Call dispatch() with job instance	dispatch($emailJob)	Job sent to queue system
3	Queue stores job	Job added to queue storage	Job waits in queue
4	Queue worker fetches job	Worker polls queue	Job retrieved for processing
5	Worker executes job handle()	SendEmail::handle()	Email sent to user
6	Job completes	No errors	Job removed from queue

💡 Job completes successfully or fails after execution

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	Final
$emailJob	undefined	SendEmail object with user	Same object dispatched	Stored in queue	Fetched by worker	Executing handle()	Job done

Key Moments - 3 Insights

Why doesn't dispatch() immediately run the job code?

dispatch() only sends the job to the queue for later processing by a worker, as shown in steps 2 and 3 of the execution_table.

What happens if no queue worker is running?

The job stays in the queue waiting, as shown in step 3, until a worker picks it up in step 4.

How does the job know what code to run?

The job class has a handle() method that the worker calls to execute the job, shown in step 5.

Visual Quiz - 3 Questions

Look at the execution_table, what is the state of the job after step 3?

A Job is waiting in the queue

B Job is executing handle()

C Job has been removed from queue

D Job instance is not created yet

💡 Hint

Check the 'Result' column in row 3 of the execution_table

At which step does the queue worker pick up the job for processing?

A Step 2

B Step 4

C Step 5

D Step 6

💡 Hint

Look at the 'Action' column for when the worker fetches the job

If dispatch() was not called, what would happen to the job object?

A It would be immediately executed

B It would be stored in the queue

C It would not be sent to the queue or executed

D It would fail automatically

💡 Hint

Refer to step 2 where dispatch() sends the job to the queue

Concept Snapshot

Dispatching jobs in Laravel:
- Create a job class with a handle() method
- Instantiate the job with needed data
- Use dispatch() to send job to queue
- Queue worker picks job and runs handle()
- Job runs asynchronously, not immediately
- Jobs stay in queue until processed

Full Transcript

Dispatching jobs in Laravel means creating a job class that holds the code to run later. You make a job object with any data it needs. Then you call dispatch() with that job. This sends the job to a queue system, which stores it until a queue worker picks it up. The worker runs the job's handle() method to do the work, like sending an email. The job finishes and is removed from the queue. This lets your app do tasks in the background without waiting.