{"id":605,"date":"2025-09-02T11:26:26","date_gmt":"2025-09-02T11:26:26","guid":{"rendered":"https:\/\/1v0.net\/blog\/?p=605"},"modified":"2025-09-02T11:26:29","modified_gmt":"2025-09-02T11:26:29","slug":"how-to-schedule-jobs-in-laravel-with-task-scheduling","status":"publish","type":"post","link":"https:\/\/1v0.net\/blog\/how-to-schedule-jobs-in-laravel-with-task-scheduling\/","title":{"rendered":"How to Schedule Jobs in Laravel with Task Scheduling"},"content":{"rendered":"\n

Laravel\u2019s task scheduling system allows you to automate repetitive jobs such as clearing caches, sending out reports, or syncing data. Instead of creating multiple cron jobs on the server, you define all of your scheduled tasks in code and keep them version controlled. This makes it easier to manage and deploy automation tasks consistently.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Setting Up the Scheduler<\/strong><\/h2>\n\n\n
* * * * * php \/path-to-your-app\/artisan schedule:run >> \/dev\/null 2>&1<\/code><\/span>Code language:<\/span> Bash<\/span> (<\/span>bash<\/span>)<\/span><\/small><\/pre>\n\n\n
You only need a single cron entry that runs Laravel\u2019s scheduler every minute. From there, Laravel decides which tasks need to execute. This approach keeps your automation clean and centralized inside your application.<\/p>\n\n\n\n
<\/div>\n\n\n\n
Defining Scheduled Tasks<\/strong><\/h2>\n\n\n
\/\/ app\/Console\/Kernel.php<\/span>\n\nprotected<\/span> function<\/span> schedule<\/span>(Schedule $schedule)<\/span>\n<\/span>{\n    $schedule->command('emails:send'<\/span>)->dailyAt('09:00'<\/span>);\n    $schedule->job(new<\/span> CleanUpTempFiles)->hourly();\n}<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
You define tasks inside app\/Console\/Kernel.php<\/code> using the schedule<\/code> method. You can schedule Artisan commands, queued jobs, or closures. Laravel provides methods like dailyAt()<\/code>, hourly()<\/code>, and weeklyOn()<\/code> to customize when tasks run.<\/p>\n\n\n\n
<\/div>\n\n\n\n
Different Frequency Options<\/strong><\/h2>\n\n\n
$schedule->command('cache:clear'<\/span>)->everyMinute();\n$schedule->command('backup:run'<\/span>)->twiceDaily(1<\/span>, 13<\/span>);\n$schedule->command('reports:send'<\/span>)->weeklyOn(1<\/span>, '08:00'<\/span>); \/\/ Monday 8am<\/span>\n$schedule->command('cleanup:archive'<\/span>)->monthlyOn(1<\/span>, '02:00'<\/span>);<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Laravel includes expressive frequency methods to fit your use case. You can schedule tasks every minute, twice daily, weekly on a specific day, or monthly at a given time.<\/p>\n\n\n\n
<\/div>\n\n\n\n
Environment-Based Scheduling<\/strong><\/h2>\n\n\n
$schedule->command('emails:send'<\/span>)\n    ->daily()\n    ->environments(['production'<\/span>]);<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
You can restrict tasks to specific environments. For example, you may want to send emails only in production and skip them in your local or staging environments.<\/p>\n\n\n\n
<\/div>\n\n\n\n
Output Logging<\/strong><\/h2>\n\n\n
$schedule->command('reports:generate'<\/span>)\n    ->daily()\n    ->appendOutputTo(storage_path('logs\/schedule.log'<\/span>));<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
When running scheduled commands, capturing their output helps with debugging. Use appendOutputTo()<\/code> or sendOutputTo()<\/code> to direct the output to log files.<\/p>\n\n\n\n
<\/div>\n\n\n\n
Practical Maintenance Tasks<\/strong><\/h2>\n\n\n
$schedule->command('model:prune'<\/span>)->daily();\n$schedule->command('cache:clear'<\/span>)->weekly();\n$schedule->command('db:backup'<\/span>)->dailyAt('01:00'<\/span>);<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Typical tasks include pruning old models, clearing caches, or running database backups. Automating these jobs improves reliability and reduces manual overhead.<\/p>\n\n\n\n
<\/div>\n\n\n\n
Using Closures in Scheduling<\/strong><\/h2>\n\n\n
$schedule->call(function<\/span> ()<\/span> <\/span>{\n    \\Log::info('Scheduled closure executed at '<\/span> . now());\n})->everyFiveMinutes();<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Closures let you define quick tasks inline without creating full commands. This is useful for logging, temporary cleanups, or testing scheduled execution.<\/p>\n\n\n\n
<\/div>\n\n\n\n
Running Scheduled Events in the Background<\/strong><\/h2>\n\n\n
$schedule->command('reports:generate'<\/span>)\n    ->dailyAt('23:00'<\/span>)\n    ->withoutOverlapping()\n    ->runInBackground();<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
withoutOverlapping()<\/code> ensures that a job won\u2019t run again if the previous instance hasn\u2019t finished. Adding runInBackground()<\/code> allows long-running tasks to execute without blocking others.<\/p>\n\n\n\n
<\/div>\n\n\n\n
Building a UI to Track Completed Jobs<\/strong><\/h2>\n\n\n\n
Sometimes you need visibility into which scheduled tasks or queued jobs have already run. While Laravel Horizon provides a great dashboard, you can also build a lightweight UI yourself for audit and monitoring purposes.<\/p>\n\n\n\n
Migration: Job Runs Table<\/strong><\/h3>\n\n\n
\/\/ database\/migrations\/2025_09_02_000001_create_job_runs_table.php<\/span>\nSchema::create('job_runs'<\/span>, function<\/span> (Blueprint $table)<\/span> <\/span>{\n    $table->id();\n    $table->string('job_name'<\/span>);\n    $table->string('queue'<\/span>)->nullable();\n    $table->timestamp('started_at'<\/span>)->nullable();\n    $table->timestamp('finished_at'<\/span>)->nullable();\n    $table->unsignedInteger('duration_ms'<\/span>)->nullable();\n    $table->string('status'<\/span>); \/\/ success | failed<\/span>\n    $table->longText('exception'<\/span>)->nullable();\n    $table->timestamps();\n});<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
This table logs each executed job with status, duration, and exception details if applicable.<\/p>\n\n\n\n
Queue Events<\/strong><\/h3>\n\n\n
\/\/ app\/Providers\/EventServiceProvider.php<\/span>\nuse<\/span> Illuminate<\/span>\\Support<\/span>\\Facades<\/span>\\Queue<\/span>;\nuse<\/span> Illuminate<\/span>\\Queue<\/span>\\Events<\/span>\\JobProcessed<\/span>;\nuse<\/span> Illuminate<\/span>\\Queue<\/span>\\Events<\/span>\\JobFailed<\/span>;\n\npublic<\/span> function<\/span> boot<\/span>()<\/span>: void<\/span>\n<\/span>{\n    Queue::after(function<\/span> (JobProcessed $event)<\/span> <\/span>{\n        \\App\\Models\\JobRun::create([\n            'job_name'<\/span> => $event->job->resolveName(),\n            'status'<\/span> => 'success'<\/span>,\n            'started_at'<\/span> => now()->subSeconds(1<\/span>),\n            'finished_at'<\/span> => now(),\n        ]);\n    });\n\n    Queue::failing(function<\/span> (JobFailed $event)<\/span> <\/span>{\n        \\App\\Models\\JobRun::create([\n            'job_name'<\/span> => $event->job->resolveName(),\n            'status'<\/span> => 'failed'<\/span>,\n            'exception'<\/span> => $event->exception->getMessage(),\n        ]);\n    });\n}<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Here we listen to job lifecycle events and insert records into the job_runs<\/code> table. You can enrich it with duration, queue name, or custom tags.<\/p>\n\n\n\n
Blade UI Example<\/strong><\/h3>\n\n\n
\/\/ resources\/views\/job-runs\/index.blade.php<\/span>\n<table class<\/span>=\"table<\/span>-auto<\/span> w<\/span>-full<\/span>\">\n  <thead<\/span>>\n    <tr<\/span>>\n      <th<\/span>>Job<\/span> Name<\/span><\/th<\/span>>\n      <th<\/span>>Status<\/span><\/th<\/span>>\n      <th<\/span>>Started<\/span><\/th<\/span>>\n      <th<\/span>>Finished<\/span><\/th<\/span>>\n      <th<\/span>>Error<\/span><\/th<\/span>>\n    <\/tr<\/span>>\n  <\/thead<\/span>>\n  <tbody<\/span>>\n    @foreach<\/span>($runs<\/span> as<\/span> $run<\/span>)\n    <tr<\/span>>\n      <td<\/span>><\/span>{{ $run->job_name }}<\/td>\n      <td>{{ $run->status }}<\/td>\n      <td>{{ $run->started_at }}<\/td>\n      <td>{{ $run->finished_at }}<\/td>\n      <td>{{ $run->exception }}<\/td>\n    <\/tr>\n    @endforeach<\/span>\n  <\/tbody>\n<\/table><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
This Blade view lists job history, making it easy to monitor success\/failure patterns. You can add pagination, filtering, or search for larger datasets.<\/p>\n\n\n\n
<\/div>\n\n\n\n
Wrapping Up<\/strong><\/h2>\n\n\n\n
Laravel\u2019s scheduler streamlines automation by letting you manage all recurring jobs inside your codebase. With support for different frequencies, environment restrictions, logging, and background execution, you can cover almost any use case. For visibility, building a simple UI to list completed jobs ensures transparency and helps with debugging and auditing.<\/p>\n\n\n\n
<\/div>\n\n\n\n
What\u2019s Next<\/strong><\/h2>\n\n\n\n
To keep building robust background processes and automation, explore these articles:<\/p>\n\n\n\n