Handle Error Of Notification Queue if It fails | Logging instead of Throwing The Error And Stopped The Rest Codes Execution

I was able to make it work by adding this handle method in the Notification class. This way is not that nice since the handle method should be added on every Notification class.

It would be better if it works with try-catch block which we could implement it once while notifying the user. I tested this (try-catch) but not working at that time maybe because of the cache or that literally does not support the queues. Everyone having the same issue could try what @tisuchi commented as well. Just FYI.

Handle method inside Notification class

public function handle($notifiable, Throwable $exception)
{
    Log::error('Failed to send notification: ' . $exception->getMessage());
}

@uminnkhantnaing - Adding the handle method is unfortunately not working for me. The exception is getting thrown as usual, and anything I add to my handle method isn't being run.

I can access exceptions thrown to the "failed" method, but can't prevent them from being thrown to the error log.

Using Laravel 11 and Mailhog for testing.

Following up, found a cleaner solution.

If there is a specific error you are trying to avoid, you can configure that in the global exception handler. Since I upgraded from Laravel 10 -> 11, I'm using Laravel 10's exception structure. So added protected $dontReport to App\Exceptions\Handler.php.

For Laravel 11, syntax would be here. https://laravel.com/docs/11.x/errors#ignoring-exceptions-by-type

protected $dontReport = [
        InvalidEmailException::class,
];

This method still shows the exception in the "failed" method on the notification still allows me catch the exception and do something with it. Just won't throw it to the log channels.

    public function failed(Throwable $e) {
        if ($e instanceof PostmarkTransportException) {
            // do something with it
        }
    }

Found a flexible way to allow all channels to attempt sending, even if one fails. This approach also lets you handle specific errors (e.g., clearing an FCM token upon failure). The core idea is to override the Notification class to set a temporary channel and create a custom NotificationService that iterates through each channel by setting the temporary channel .

class NotificationService
{
    public function notify(object $notifiable, BaseNotification $notification)
    {
        $listOfChannels = $notification->via($notifiable);
        foreach ($listOfChannels as $channel) {
            $notification->setCurrentChannel($channel);
            try {
                $notifiable->notify($notification);
            } catch (CouldNotSendNotification $e) {
                // TODO: specific error handling (e.g., clear FCM token)
            } catch (\Exception $e) {
                // TODO: general error handling
            }
        }
        $notification->clearCurrentChannel();
    }
}

class BaseNotification extends Notification
{
    public string $currentChannel;

    public function via($notifiable)
    {
        return $this->currentChannel ? [$this->currentChannel] : ['database', 'mail', FcmChannel::class];
    }

    public function setCurrentChannel(string $channel): void
    {
        $this->currentChannel = $channel;
    }

    public function getCurrentChannel(): string
    {
        return $this->currentChannel;
    }

    public function clearCurrentChannel(): void
    {
        $this->currentChannel = '';
    }
}

class MyProgramOrJob {
    public function run()
    {
        // $notifiable  
        // $notification - you custom notificaiton that extend BaseNotification

        (new NotificationService)->notify(
            $notifiable, 
            $notification,
        );
    }
}