Failed job handling in Laravel - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to dispatch a job that will be retried on failure.

Laravel

<?php
use App\Jobs\ProcessOrder;

ProcessOrder::dispatch()->[1]();

Drag options to blanks, or click blank then click option'

Adelay

BonQueue

CallOnQueue

Dretry

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'retry' method which does not exist on dispatch.

Confusing 'onQueue' with retry behavior.

The delay() method schedules the job to run after a delay, which helps in retrying failed jobs later.

2fill in blank

medium

Complete the code to listen for failed jobs and log the failure.

Laravel

use Illuminate\Queue\Events\JobFailed;

Queue::failing(function (JobFailed $event) {
    Log::error('Job failed: ' . $event->job->[1]());
});

Drag options to blanks, or click blank then click option'

AgetJobId

BgetName

CgetQueue

DgetConnectionName

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'getJobId' which returns an ID, not the job name.

Using 'getQueue' which returns the queue name, not the job.

The getName() method returns the name of the failed job, useful for logging.

3fill in blank

hard

Fix the error in the code to retry a failed job after 10 seconds.

Laravel

public function failed()
{
    $this->release([1]);
}

Drag options to blanks, or click blank then click option'

A'10 seconds'

Bnow()->addSeconds(10)

C10

D10 * 1000

Attempts:

3 left

💡 Hint

Common Mistakes

Passing a string like '10 seconds' causes errors.

Passing a DateTime object instead of seconds.

The release() method expects an integer number of seconds to delay the retry.

4fill in blank

hard

Fill both blanks to define a job class that handles failure by logging and releasing after delay.

Laravel

class ProcessPayment implements ShouldQueue
{
    public function failed(Exception $exception)
    {
        Log::error($exception->getMessage());
        $this->[1]([2]);
    }
}

Drag options to blanks, or click blank then click option'

Arelease

Bdelete

C10

D5

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'delete' instead of 'release' will remove the job.

Using too small or string delay values.

The release(10) method retries the job after 10 seconds delay.

5fill in blank

hard

Fill all three blanks to create a failed job listener that logs and notifies admin.

Laravel

Queue::failing(function (JobFailed $event) {
    Log::error('Failed job: ' . $event->job->[1]());
    Notification::route('mail', '[e-mail]')->[2](
        new JobFailedNotification($event->job, $event->exception)
    );
    $event->job->[3]();
});

Drag options to blanks, or click blank then click option'

AgetName

Bnotify

Cdelete

Drelease

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'release' instead of 'delete' will retry the job.

Using wrong method names for notification.

This code logs the failed job name, sends a notification, and deletes the failed job from the queue.

Practice

1. What is the primary purpose of the failed() method in a Laravel job class?

easy

A. To list all failed jobs in the queue

B. To retry a failed job automatically

C. To define actions when a queued job fails during execution

D. To clear all failed jobs from the database

Solution

1. Step 1: Understand the role of failed() method

   The failed() method is a special method in Laravel job classes that runs when the job fails after all retry attempts.

2. Step 2: Identify what failed() does

   This method allows you to define custom logic like sending notifications or logging when a job fails.

3. Final Answer:

   To define actions when a queued job fails during execution -> Option C

4. Quick Check:

   failed() handles failure actions [OK]

Hint: Remember: failed() runs only on job failure [OK]

Common Mistakes:

• Confusing failed() with retry commands
• Thinking it lists or clears failed jobs
• Assuming it runs on successful job completion

2. Which of the following is the correct Artisan command to retry all failed jobs in Laravel?

easy

A. php artisan queue:retry all

B. php artisan queue:retry --all

C. php artisan queue:retry --failed

D. php artisan queue:retry --all-jobs

Solution

1. Step 1: Recall the syntax for retrying failed jobs

   Laravel's command to retry failed jobs is php artisan queue:retry followed by the job IDs or all to retry all.

2. Step 2: Identify the correct option

   The correct command to retry all failed jobs is php artisan queue:retry all.

3. Final Answer:

   php artisan queue:retry all -> Option A

4. Quick Check:

   Retry all failed jobs = queue:retry all [OK]

Hint: Use 'all' after retry to retry every failed job [OK]

Common Mistakes:

• Adding extra flags like --all or --failed which don't exist
• Using incorrect command syntax
• Confusing retry with clear commands

3. Given this Laravel job class snippet, what will happen when the job fails?

class SendEmailJob implements ShouldQueue {
    public function handle() {
        // code that throws an exception
    }
    public function failed(Exception $exception) {
        Log::error('Email sending failed: ' . $exception->getMessage());
    }
}

medium

A. The job will be retried indefinitely without logging

B. The job will succeed despite the exception

C. The job will be removed silently without any action

D. The job failure will be logged with the error message

Solution

1. Step 1: Analyze the failed() method implementation

   The failed() method logs an error message when the job fails due to an exception.

2. Step 2: Understand job failure behavior

   When the job throws an exception, Laravel calls failed() and logs the failure message.

3. Final Answer:

   The job failure will be logged with the error message -> Option D

4. Quick Check:

   failed() logs failure message [OK]

Hint: Check if failed() logs or retries [OK]

Common Mistakes:

• Assuming job retries indefinitely without limit
• Thinking failure is ignored without logging
• Believing job succeeds despite exception

4. Consider this command to clear failed jobs:

php artisan queue:flush

What is the issue with this command?

medium

A. It clears all failed jobs correctly

B. The command does not exist; the correct command is queue:forget

C. It retries all failed jobs instead of clearing

D. It only clears jobs from the default queue, not all queues

Solution

1. Step 1: Verify the correct command to clear failed jobs

   The php artisan queue:flush command does not exist in Laravel. The correct command to remove failed jobs is php artisan queue:forget {id} for specific jobs or manually clearing the failed_jobs table.

2. Step 2: Confirm the issue

   Since queue:flush is not a valid command, it cannot clear failed jobs.

3. Final Answer:

   The command does not exist; the correct command is queue:forget -> Option B

4. Quick Check:

   queue:flush is invalid; use queue:forget [OK]

Hint: Remember: queue:flush is not a valid Artisan command [OK]

Common Mistakes:

• Thinking queue:flush does not exist
• Confusing it with queue:forget for specific jobs
• Mistaking it for a retry command

5. You want to notify the admin by email whenever a job fails in Laravel. Which approach correctly implements this using the failed() method?

hard

A. Add a failed() method in the job class that sends an email notification to the admin

B. Use php artisan queue:notify-admin command after job failure

C. Configure the failed_jobs table to send emails automatically

D. Set notify_admin = true in the job constructor

Solution

1. Step 1: Understand how to handle job failure notifications

   Laravel allows defining a failed() method in job classes to run custom logic on failure, such as sending emails.

2. Step 2: Identify the correct implementation

   Adding a failed() method that sends an email notification to the admin is the correct way to notify on failure.

3. Final Answer:

   Add a failed() method in the job class that sends an email notification to the admin -> Option A

4. Quick Check:

   Use failed() to notify admin on job failure [OK]

Hint: Put notification code inside failed() method [OK]

Common Mistakes:

• Expecting Artisan commands to notify admin automatically
• Assuming database config sends emails
• Trying to set flags in constructor for notifications