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.

Practice

1. What is the main purpose of dispatching jobs in Laravel?

easy

A. To handle user authentication

B. To run tasks in the background without blocking user requests

C. To create database tables automatically

D. To directly output data to the browser

Solution

1. Step 1: Understand what dispatching jobs means

   Dispatching jobs means sending tasks to run in the background, separate from the main app flow.

2. Step 2: Identify the benefit of background jobs

   Running tasks in the background improves app speed and user experience by not blocking user requests.

3. Final Answer:

   To run tasks in the background without blocking user requests -> Option B

4. Quick Check:

   Dispatching jobs = background tasks [OK]

Hint: Jobs run in background to keep app fast and responsive [OK]

Common Mistakes:

• Thinking dispatching jobs outputs data immediately
• Confusing jobs with database migrations
• Assuming jobs handle user login

2. Which is the correct way to dispatch a job called SendEmailJob in Laravel?

easy

A. SendEmailJob.dispatch();

B. dispatch SendEmailJob();

C. SendEmailJob::dispatch();

D. dispatch::SendEmailJob();

Solution

1. Step 1: Recall Laravel job dispatch syntax

   Laravel uses the static method ::dispatch() on the job class to send it to the queue.

2. Step 2: Match the syntax to the options

   SendEmailJob::dispatch(); uses SendEmailJob::dispatch(); which is the correct Laravel syntax.

3. Final Answer:

   SendEmailJob::dispatch(); -> Option C

4. Quick Check:

   JobClass::dispatch() = correct syntax [OK]

Hint: Use ClassName::dispatch() to send jobs [OK]

Common Mistakes:

• Using dot instead of double colon for static call
• Trying to call dispatch as a function without ::
• Incorrect order or missing parentheses

3. Given this code:

SendReportJob::dispatch();
return 'Report sent';

What will the user see immediately after this code runs?

medium

A. The report is sent and user sees 'Report sent' immediately

B. The user waits until the report is sent, then sees 'Report sent'

C. An error because dispatch() is not a valid method

D. Nothing happens because dispatch() does not run the job

Solution

1. Step 1: Understand dispatch() behavior

   Dispatching a job sends it to the queue to run in the background immediately without blocking.

2. Step 2: Analyze the return statement

   The return 'Report sent' runs right after dispatch(), so the user sees this message immediately.

3. Final Answer:

   The report is sent and user sees 'Report sent' immediately -> Option A

4. Quick Check:

   dispatch() runs background job, return runs immediately [OK]

Hint: dispatch() queues job; return runs right after [OK]

Common Mistakes:

• Thinking dispatch() waits for job to finish
• Assuming dispatch() causes an error
• Believing dispatch() does nothing

4. What is wrong with this code snippet?

dispatch SendEmailJob();

medium

A. dispatch is not a function, should use SendEmailJob::dispatch()

B. Missing parentheses after dispatch

C. SendEmailJob must be instantiated with new keyword

D. dispatch should be lowercase

Solution

1. Step 1: Check dispatch usage

   In Laravel, dispatching a job is done by calling ::dispatch() on the job class, not by calling dispatch as a function.

2. Step 2: Identify the error in the code

   The code tries to call dispatch as a function without parentheses and without using the static method on the job class.

3. Final Answer:

   dispatch is not a function, should use SendEmailJob::dispatch() -> Option A

4. Quick Check:

   Use JobClass::dispatch() not dispatch function [OK]

Hint: dispatch() is a static method on job class, not a function [OK]

Common Mistakes:

• Calling dispatch as a standalone function
• Forgetting :: before dispatch
• Trying to instantiate job without dispatch

5. You want to dispatch a job ProcessOrderJob with an order ID parameter 123. Which code correctly dispatches this job with the parameter?

hard

A. ProcessOrderJob::dispatch()->with(123);

B. dispatch(ProcessOrderJob(123));

C. ProcessOrderJob->dispatch(123);

D. ProcessOrderJob::dispatch(123);

Solution

1. Step 1: Understand how to pass parameters to jobs

   Jobs accept constructor parameters, and dispatch() forwards them to the constructor.

2. Step 2: Match correct syntax

   ProcessOrderJob::dispatch(123); calls ProcessOrderJob::dispatch(123); which passes 123 to the job constructor correctly.

3. Final Answer:

   ProcessOrderJob::dispatch(123); -> Option D

4. Quick Check:

   dispatch(params) passes args to job constructor [OK]

Hint: Pass parameters inside dispatch() to send to job constructor [OK]

Common Mistakes:

• Trying to call dispatch on an instance
• Using dispatch as a function with wrong syntax
• Chaining with() method which does not exist