Task Scheduling

• Introduction
• Defining Schedules
  • Scheduling Artisan Commands
  • Scheduling Queued Jobs
  • Scheduling Shell Commands
  • Schedule Frequency Options
  • Timezones
  • Preventing Task Overlaps
  • Running Tasks on One Server
  • Background Tasks
  • Maintenance Mode
• Running the Scheduler
  • Sub-Minute Scheduled Tasks
  • Running the Scheduler Locally
• Task Output
• Task Hooks
• Events

Introduction

In the past, you may have written a cron configuration entry for each task you needed to schedule on your server. However, this can quickly become a pain because your task schedule is no longer in source control and you must SSH into your server to view your existing cron entries or add additional entries.

Laravel's command scheduler offers a fresh approach to managing scheduled tasks on your server. The scheduler allows you to fluently and expressively define your command schedule within your Laravel application itself. When using the scheduler, only a single cron entry is needed on your server. Your task schedule is defined in the app/Console/Kernel.php file's schedule method. To help you get started, a simple example is defined within the method.

Defining Schedules

You may define all of your scheduled tasks in the schedule method of your application's App\Console\Kernel class. To get started, let's take a look at an example. In this example, we will schedule a closure to be called every day at midnight. Within the closure we will execute a database query to clear a table:

 1<?php
 2 
 3namespace App\Console;
 4 
 5use Illuminate\Console\Scheduling\Schedule;
 6use Illuminate\Foundation\Console\Kernel as ConsoleKernel;
 7use Illuminate\Support\Facades\DB;
 8 
 9class Kernel extends ConsoleKernel
10{
11    /**
12     * Define the application's command schedule.
13     */
14    protected function schedule(Schedule $schedule): void
15    {
16        $schedule->call(function () {
17            DB::table('recent_users')->delete();
18        })->daily();
19    }
20}
 1<?php
 2 
 3namespace App\Console;
 4 
 5use Illuminate\Console\Scheduling\Schedule;
 6use Illuminate\Foundation\Console\Kernel as ConsoleKernel;
 7use Illuminate\Support\Facades\DB;
 8 
 9class Kernel extends ConsoleKernel
10{
11    /**
12     * Define the application's command schedule.
13     */
14    protected function schedule(Schedule $schedule): void
15    {
16        $schedule->call(function () {
17            DB::table('recent_users')->delete();
18        })->daily();
19    }
20}

In addition to scheduling using closures, you may also schedule invokable objects. Invokable objects are simple PHP classes that contain an __invoke method:

1$schedule->call(new DeleteRecentUsers)->daily();
1$schedule->call(new DeleteRecentUsers)->daily();

If you would like to view an overview of your scheduled tasks and the next time they are scheduled to run, you may use the schedule:list Artisan command:

1php artisan schedule:list
1php artisan schedule:list

Scheduling Artisan Commands

In addition to scheduling closures, you may also schedule Artisan commands and system commands. For example, you may use the command method to schedule an Artisan command using either the command's name or class.

When scheduling Artisan commands using the command's class name, you may pass an array of additional command-line arguments that should be provided to the command when it is invoked:

1use App\Console\Commands\SendEmailsCommand;
2 
3$schedule->command('emails:send Taylor --force')->daily();
4 
5$schedule->command(SendEmailsCommand::class, ['Taylor', '--force'])->daily();
1use App\Console\Commands\SendEmailsCommand;
2 
3$schedule->command('emails:send Taylor --force')->daily();
4 
5$schedule->command(SendEmailsCommand::class, ['Taylor', '--force'])->daily();

Scheduling Queued Jobs

The job method may be used to schedule a queued job. This method provides a convenient way to schedule queued jobs without using the call method to define closures to queue the job:

1use App\Jobs\Heartbeat;
2 
3$schedule->job(new Heartbeat)->everyFiveMinutes();
1use App\Jobs\Heartbeat;
2 
3$schedule->job(new Heartbeat)->everyFiveMinutes();

Optional second and third arguments may be provided to the job method which specifies the queue name and queue connection that should be used to queue the job:

1use App\Jobs\Heartbeat;
2 
3// Dispatch the job to the "heartbeats" queue on the "sqs" connection...
4$schedule->job(new Heartbeat, 'heartbeats', 'sqs')->everyFiveMinutes();
1use App\Jobs\Heartbeat;
2 
3// Dispatch the job to the "heartbeats" queue on the "sqs" connection...
4$schedule->job(new Heartbeat, 'heartbeats', 'sqs')->everyFiveMinutes();

Scheduling Shell Commands

The exec method may be used to issue a command to the operating system:

1$schedule->exec('node /home/forge/script.js')->daily();
1$schedule->exec('node /home/forge/script.js')->daily();

Schedule Frequency Options

We've already seen a few examples of how you may configure a task to run at specified intervals. However, there are many more task schedule frequencies that you may assign to a task:

These methods may be combined with additional constraints to create even more finely tuned schedules that only run on certain days of the week. For example, you may schedule a command to run weekly on Monday:

 1// Run once per week on Monday at 1 PM...
 2$schedule->call(function () {
 3    // ...
 4})->weekly()->mondays()->at('13:00');
 5 
 6// Run hourly from 8 AM to 5 PM on weekdays...
 7$schedule->command('foo')
 8          ->weekdays()
 9          ->hourly()
10          ->timezone('America/Chicago')
11          ->between('8:00', '17:00');
 1// Run once per week on Monday at 1 PM...
 2$schedule->call(function () {
 3    // ...
 4})->weekly()->mondays()->at('13:00');
 5 
 6// Run hourly from 8 AM to 5 PM on weekdays...
 7$schedule->command('foo')
 8          ->weekdays()
 9          ->hourly()
10          ->timezone('America/Chicago')
11          ->between('8:00', '17:00');

A list of additional schedule constraints may be found below:

Day Constraints

The days method may be used to limit the execution of a task to specific days of the week. For example, you may schedule a command to run hourly on Sundays and Wednesdays:

1$schedule->command('emails:send')
2                ->hourly()
3                ->days([0, 3]);
1$schedule->command('emails:send')
2                ->hourly()
3                ->days([0, 3]);

Alternatively, you may use the constants available on the Illuminate\Console\Scheduling\Schedule class when defining the days on which a task should run:

1use Illuminate\Console\Scheduling\Schedule;
2 
3$schedule->command('emails:send')
4                ->hourly()
5                ->days([Schedule::SUNDAY, Schedule::WEDNESDAY]);
1use Illuminate\Console\Scheduling\Schedule;
2 
3$schedule->command('emails:send')
4                ->hourly()
5                ->days([Schedule::SUNDAY, Schedule::WEDNESDAY]);

Between Time Constraints

The between method may be used to limit the execution of a task based on the time of day:

1$schedule->command('emails:send')
2                    ->hourly()
3                    ->between('7:00', '22:00');
1$schedule->command('emails:send')
2                    ->hourly()
3                    ->between('7:00', '22:00');

Similarly, the unlessBetween method can be used to exclude the execution of a task for a period of time:

1$schedule->command('emails:send')
2                    ->hourly()
3                    ->unlessBetween('23:00', '4:00');
1$schedule->command('emails:send')
2                    ->hourly()
3                    ->unlessBetween('23:00', '4:00');

Truth Test Constraints

The when method may be used to limit the execution of a task based on the result of a given truth test. In other words, if the given closure returns true, the task will execute as long as no other constraining conditions prevent the task from running:

1$schedule->command('emails:send')->daily()->when(function () {
2    return true;
3});
1$schedule->command('emails:send')->daily()->when(function () {
2    return true;
3});

The skip method may be seen as the inverse of when. If the skip method returns true, the scheduled task will not be executed:

1$schedule->command('emails:send')->daily()->skip(function () {
2    return true;
3});
1$schedule->command('emails:send')->daily()->skip(function () {
2    return true;
3});

When using chained when methods, the scheduled command will only execute if all when conditions return true.

Environment Constraints

The environments method may be used to execute tasks only on the given environments (as defined by the APP_ENV environment variable):

1$schedule->command('emails:send')
2            ->daily()
3            ->environments(['staging', 'production']);
1$schedule->command('emails:send')
2            ->daily()
3            ->environments(['staging', 'production']);

Timezones

Using the timezone method, you may specify that a scheduled task's time should be interpreted within a given timezone:

1$schedule->command('report:generate')
2         ->timezone('America/New_York')
3         ->at('2:00')
1$schedule->command('report:generate')
2         ->timezone('America/New_York')
3         ->at('2:00')

If you are repeatedly assigning the same timezone to all of your scheduled tasks, you may wish to define a scheduleTimezone method in your App\Console\Kernel class. This method should return the default timezone that should be assigned to all scheduled tasks:

1use DateTimeZone;
2 
3/**
4 * Get the timezone that should be used by default for scheduled events.
5 */
6protected function scheduleTimezone(): DateTimeZone|string|null
7{
8    return 'America/Chicago';
9}
1use DateTimeZone;
2 
3/**
4 * Get the timezone that should be used by default for scheduled events.
5 */
6protected function scheduleTimezone(): DateTimeZone|string|null
7{
8    return 'America/Chicago';
9}

[!WARNING]
Remember that some timezones utilize daylight savings time. When daylight saving time changes occur, your scheduled task may run twice or even not run at all. For this reason, we recommend avoiding timezone scheduling when possible.

Preventing Task Overlaps

By default, scheduled tasks will be run even if the previous instance of the task is still running. To prevent this, you may use the withoutOverlapping method:

1$schedule->command('emails:send')->withoutOverlapping();
1$schedule->command('emails:send')->withoutOverlapping();

In this example, the emails:send Artisan command will be run every minute if it is not already running. The withoutOverlapping method is especially useful if you have tasks that vary drastically in their execution time, preventing you from predicting exactly how long a given task will take.

If needed, you may specify how many minutes must pass before the "without overlapping" lock expires. By default, the lock will expire after 24 hours:

1$schedule->command('emails:send')->withoutOverlapping(10);
1$schedule->command('emails:send')->withoutOverlapping(10);

Behind the scenes, the withoutOverlapping method utilizes your application's cache to obtain locks. If necessary, you can clear these cache locks using the schedule:clear-cache Artisan command. This is typically only necessary if a task becomes stuck due to an unexpected server problem.

Running Tasks on One Server

[!WARNING]
To utilize this feature, your application must be using the database, memcached, dynamodb, or redis cache driver as your application's default cache driver. In addition, all servers must be communicating with the same central cache server.

If your application's scheduler is running on multiple servers, you may limit a scheduled job to only execute on a single server. For instance, assume you have a scheduled task that generates a new report every Friday night. If the task scheduler is running on three worker servers, the scheduled task will run on all three servers and generate the report three times. Not good!

To indicate that the task should run on only one server, use the onOneServer method when defining the scheduled task. The first server to obtain the task will secure an atomic lock on the job to prevent other servers from running the same task at the same time:

1$schedule->command('report:generate')
2                ->fridays()
3                ->at('17:00')
4                ->onOneServer();
1$schedule->command('report:generate')
2                ->fridays()
3                ->at('17:00')
4                ->onOneServer();

Naming Single Server Jobs

Sometimes you may need to schedule the same job to be dispatched with different parameters, while still instructing Laravel to run each permutation of the job on a single server. To accomplish this, you may assign each schedule definition a unique name via the name method:

1$schedule->job(new CheckUptime('https://laravel.com'))
2            ->name('check_uptime:laravel.com')
3            ->everyFiveMinutes()
4            ->onOneServer();
5 
6$schedule->job(new CheckUptime('https://vapor.laravel.com'))
7            ->name('check_uptime:vapor.laravel.com')
8            ->everyFiveMinutes()
9            ->onOneServer();
1$schedule->job(new CheckUptime('https://laravel.com'))
2            ->name('check_uptime:laravel.com')
3            ->everyFiveMinutes()
4            ->onOneServer();
5 
6$schedule->job(new CheckUptime('https://vapor.laravel.com'))
7            ->name('check_uptime:vapor.laravel.com')
8            ->everyFiveMinutes()
9            ->onOneServer();

Similarly, scheduled closures must be assigned a name if they are intended to be run on one server:

1$schedule->call(fn () => User::resetApiRequestCount())
2    ->name('reset-api-request-count')
3    ->daily()
4    ->onOneServer();
1$schedule->call(fn () => User::resetApiRequestCount())
2    ->name('reset-api-request-count')
3    ->daily()
4    ->onOneServer();

Background Tasks

By default, multiple tasks scheduled at the same time will execute sequentially based on the order they are defined in your schedule method. If you have long-running tasks, this may cause subsequent tasks to start much later than anticipated. If you would like to run tasks in the background so that they may all run simultaneously, you may use the runInBackground method:

1$schedule->command('analytics:report')
2         ->daily()
3         ->runInBackground();
1$schedule->command('analytics:report')
2         ->daily()
3         ->runInBackground();

[!WARNING]
The runInBackground method may only be used when scheduling tasks via the command and exec methods.

Maintenance Mode

Your application's scheduled tasks will not run when the application is in maintenance mode, since we don't want your tasks to interfere with any unfinished maintenance you may be performing on your server. However, if you would like to force a task to run even in maintenance mode, you may call the evenInMaintenanceMode method when defining the task:

1$schedule->command('emails:send')->evenInMaintenanceMode();
1$schedule->command('emails:send')->evenInMaintenanceMode();

Running the Scheduler

Now that we have learned how to define scheduled tasks, let's discuss how to actually run them on our server. The schedule:run Artisan command will evaluate all of your scheduled tasks and determine if they need to run based on the server's current time.

So, when using Laravel's scheduler, we only need to add a single cron configuration entry to our server that runs the schedule:run command every minute. If you do not know how to add cron entries to your server, consider using a service such as Laravel Forge which can manage the cron entries for you:

1* * * * * cd /path-to-your-project && php artisan schedule:run >> /dev/null 2>&1
1* * * * * cd /path-to-your-project && php artisan schedule:run >> /dev/null 2>&1

Sub-Minute Scheduled Tasks

On most operating systems, cron jobs are limited to running a maximum of once per minute. However, Laravel's scheduler allows you to schedule tasks to run at more frequent intervals, even as often as once per second:

1$schedule->call(function () {
2    DB::table('recent_users')->delete();
3})->everySecond();
1$schedule->call(function () {
2    DB::table('recent_users')->delete();
3})->everySecond();

When sub-minute tasks are defined within your application, the schedule:run command will continue running until the end of the current minute instead of exiting immediately. This allows the command to invoke all required sub-minute tasks throughout the minute.

Since sub-minute tasks that take longer than expected to run could delay the execution of later sub-minute tasks, it is recommend that all sub-minute tasks dispatch queued jobs or background commands to handle the actual task processing:

1use App\Jobs\DeleteRecentUsers;
2 
3$schedule->job(new DeleteRecentUsers)->everyTenSeconds();
4 
5$schedule->command('users:delete')->everyTenSeconds()->runInBackground();
1use App\Jobs\DeleteRecentUsers;
2 
3$schedule->job(new DeleteRecentUsers)->everyTenSeconds();
4 
5$schedule->command('users:delete')->everyTenSeconds()->runInBackground();

Interrupting Sub-Minute Tasks

As the schedule:run command runs for the entire minute of invocation when sub-minute tasks are defined, you may sometimes need to interrupt the command when deploying your application. Otherwise, an instance of the schedule:run command that is already running would continue using your application's previously deployed code until the current minute ends.

To interrupt in-progress schedule:run invocations, you may add the schedule:interrupt command to your application's deployment script. This command should be invoked after your application is finished deploying:

1php artisan schedule:interrupt
1php artisan schedule:interrupt

Running the Scheduler Locally

Typically, you would not add a scheduler cron entry to your local development machine. Instead, you may use the schedule:work Artisan command. This command will run in the foreground and invoke the scheduler every minute until you terminate the command:

1php artisan schedule:work
1php artisan schedule:work

Task Output

The Laravel scheduler provides several convenient methods for working with the output generated by scheduled tasks. First, using the sendOutputTo method, you may send the output to a file for later inspection:

1$schedule->command('emails:send')
2         ->daily()
3         ->sendOutputTo($filePath);
1$schedule->command('emails:send')
2         ->daily()
3         ->sendOutputTo($filePath);

If you would like to append the output to a given file, you may use the appendOutputTo method:

1$schedule->command('emails:send')
2         ->daily()
3         ->appendOutputTo($filePath);
1$schedule->command('emails:send')
2         ->daily()
3         ->appendOutputTo($filePath);

Using the emailOutputTo method, you may email the output to an email address of your choice. Before emailing the output of a task, you should configure Laravel's email services:

1$schedule->command('report:generate')
2         ->daily()
3         ->sendOutputTo($filePath)
4         ->emailOutputTo('[email protected]');
1$schedule->command('report:generate')
2         ->daily()
3         ->sendOutputTo($filePath)
4         ->emailOutputTo('[email protected]');

If you only want to email the output if the scheduled Artisan or system command terminates with a non-zero exit code, use the emailOutputOnFailure method:

1$schedule->command('report:generate')
2         ->daily()
3         ->emailOutputOnFailure('[email protected]');
1$schedule->command('report:generate')
2         ->daily()
3         ->emailOutputOnFailure('[email protected]');

[!WARNING]
The emailOutputTo, emailOutputOnFailure, sendOutputTo, and appendOutputTo methods are exclusive to the command and exec methods.

Task Hooks

Using the before and after methods, you may specify code to be executed before and after the scheduled task is executed:

1$schedule->command('emails:send')
2         ->daily()
3         ->before(function () {
4             // The task is about to execute...
5         })
6         ->after(function () {
7             // The task has executed...
8         });
1$schedule->command('emails:send')
2         ->daily()
3         ->before(function () {
4             // The task is about to execute...
5         })
6         ->after(function () {
7             // The task has executed...
8         });

The onSuccess and onFailure methods allow you to specify code to be executed if the scheduled task succeeds or fails. A failure indicates that the scheduled Artisan or system command terminated with a non-zero exit code:

1$schedule->command('emails:send')
2         ->daily()
3         ->onSuccess(function () {
4             // The task succeeded...
5         })
6         ->onFailure(function () {
7             // The task failed...
8         });
1$schedule->command('emails:send')
2         ->daily()
3         ->onSuccess(function () {
4             // The task succeeded...
5         })
6         ->onFailure(function () {
7             // The task failed...
8         });

If output is available from your command, you may access it in your after, onSuccess or onFailure hooks by type-hinting an Illuminate\Support\Stringable instance as the $output argument of your hook's closure definition:

 1use Illuminate\Support\Stringable;
 2 
 3$schedule->command('emails:send')
 4         ->daily()
 5         ->onSuccess(function (Stringable $output) {
 6             // The task succeeded...
 7         })
 8         ->onFailure(function (Stringable $output) {
 9             // The task failed...
10         });
 1use Illuminate\Support\Stringable;
 2 
 3$schedule->command('emails:send')
 4         ->daily()
 5         ->onSuccess(function (Stringable $output) {
 6             // The task succeeded...
 7         })
 8         ->onFailure(function (Stringable $output) {
 9             // The task failed...
10         });

Pinging URLs

Using the pingBefore and thenPing methods, the scheduler can automatically ping a given URL before or after a task is executed. This method is useful for notifying an external service, such as Envoyer, that your scheduled task is beginning or has finished execution:

1$schedule->command('emails:send')
2         ->daily()
3         ->pingBefore($url)
4         ->thenPing($url);
1$schedule->command('emails:send')
2         ->daily()
3         ->pingBefore($url)
4         ->thenPing($url);

The pingBeforeIf and thenPingIf methods may be used to ping a given URL only if a given condition is true:

1$schedule->command('emails:send')
2         ->daily()
3         ->pingBeforeIf($condition, $url)
4         ->thenPingIf($condition, $url);
1$schedule->command('emails:send')
2         ->daily()
3         ->pingBeforeIf($condition, $url)
4         ->thenPingIf($condition, $url);

The pingOnSuccess and pingOnFailure methods may be used to ping a given URL only if the task succeeds or fails. A failure indicates that the scheduled Artisan or system command terminated with a non-zero exit code:

1$schedule->command('emails:send')
2         ->daily()
3         ->pingOnSuccess($successUrl)
4         ->pingOnFailure($failureUrl);
1$schedule->command('emails:send')
2         ->daily()
3         ->pingOnSuccess($successUrl)
4         ->pingOnFailure($failureUrl);

All of the ping methods require the Guzzle HTTP library. Guzzle is typically installed in all new Laravel projects by default, but, you may manually install Guzzle into your project using the Composer package manager if it has been accidentally removed:

1composer require guzzlehttp/guzzle
1composer require guzzlehttp/guzzle

Events

If needed, you may listen to events dispatched by the scheduler. Typically, event listener mappings will be defined within your application's App\Providers\EventServiceProvider class:

 1/**
 2 * The event listener mappings for the application.
 3 *
 4 * @var array
 5 */
 6protected $listen = [
 7    'Illuminate\Console\Events\ScheduledTaskStarting' => [
 8        'App\Listeners\LogScheduledTaskStarting',
 9    ],
10 
11    'Illuminate\Console\Events\ScheduledTaskFinished' => [
12        'App\Listeners\LogScheduledTaskFinished',
13    ],
14 
15    'Illuminate\Console\Events\ScheduledBackgroundTaskFinished' => [
16        'App\Listeners\LogScheduledBackgroundTaskFinished',
17    ],
18 
19    'Illuminate\Console\Events\ScheduledTaskSkipped' => [
20        'App\Listeners\LogScheduledTaskSkipped',
21    ],
22 
23    'Illuminate\Console\Events\ScheduledTaskFailed' => [
24        'App\Listeners\LogScheduledTaskFailed',
25    ],
26];
 1/**
 2 * The event listener mappings for the application.
 3 *
 4 * @var array
 5 */
 6protected $listen = [
 7    'Illuminate\Console\Events\ScheduledTaskStarting' => [
 8        'App\Listeners\LogScheduledTaskStarting',
 9    ],
10 
11    'Illuminate\Console\Events\ScheduledTaskFinished' => [
12        'App\Listeners\LogScheduledTaskFinished',
13    ],
14 
15    'Illuminate\Console\Events\ScheduledBackgroundTaskFinished' => [
16        'App\Listeners\LogScheduledBackgroundTaskFinished',
17    ],
18 
19    'Illuminate\Console\Events\ScheduledTaskSkipped' => [
20        'App\Listeners\LogScheduledTaskSkipped',
21    ],
22 
23    'Illuminate\Console\Events\ScheduledTaskFailed' => [
24        'App\Listeners\LogScheduledTaskFailed',
25    ],
26];