Automatically running tasks in Laravel requires setting a single cron entry first. Then, you can define the Artisan command or shell command in the schedule method of the Kernel class, and select the execution frequency and conditions. 1. Add cron entry to trigger the Laravel scheduler every minute; 2. Use the command method to define the Artisan command and specify the frequency such as daily(), hourly(), etc.; 3. Use the exec method to run the shell script, and can record the logs in combination with sendOutputTo; 4. Use withoutOverlapping to prevent tasks from overlapping; 5. Manually run schedule:run during testing and configure output notifications or logs for debugging.

Running tasks automatically in Laravel usually involves scheduling Artisan commands. Laravel has a built-in task scheduler that makes it easy to define and manage scheduled jobs without needing to manually set up cron entries on your server.

Setting Up the Scheduler

The first step is to define your scheduled tasks inside the App\Console\Kernel class's schedule method. Laravel's scheduler runs on a single cron entry, which you only need to set once on your server. This cron job calls Laravel's schedule:run command every minute, checking if any scheduled tasks should be executed.

To make this work, you need to add this line to your server's crontab:

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

This ensures Laravel checks for scheduled commands every minute.

Tip : On shared hosting, you might have a UI to set cron jobs instead of editing the crontab directly. Use the same command there.

Defining Scheduled Commands

You can schedule Artisan commands using the command method. For example, if you have a command called emails:send , you can run it daily like this:

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

There are many frequency options:

• ->hourly()
• ->daily()
• ->weekly()
• ->monthly()
• You can also use more specific methods like ->everyFiveMinutes() or ->weekdays()

If you need custom logic (like running at a specific time), chain methods like at() or twiceDaily() :

 $schedule->command('backup:database')->dailyAt('2:00');

This gives you fine control over when commands run.

Running Shell Commands

Sometimes you don't need an Artisan command — maybe you want to run a script or shell command. Laravel lets you do that too with the exec method:

 $schedule->exec('bash /path/to/script.sh')->daily();

This is useful for things like clearing cache files, syncing data, or triggering other system-level processes.

Make sure the user running the scheduler has permission to execute those commands. Also, remember to log output if needed for debugging:

 $schedule->exec('python /scripts/data_sync.py')
         ->daily()
         ->sendOutputTo('/storage/logs/sync.log');

This helps track what happened if something goes wrong.

Testing and Debugging Scheduled Tasks

It's easy to forget that scheduled tasks only run when the scheduler is triggered. If you're testing locally, you can manually trigger the scheduler with:

 php artisan schedule:run

Also, make sure your command outputs something or logs results so you can verify they're working. Laravel provides two helpful methods:

• ->emailOutputTo('you@example.com')
• ->sendOutputTo($filePath)

These help capture output for review.

Gotcha : Some hosts disable email sending by default, so test that separately if you rely on email notifications.

Another thing to watch: overlapping tasks. If a command takes longer than the interval (eg, a five-minute task scheduled every minute), it could cause issues. Use ->withoutOverlapping() to prevent that:

 $schedule->command('data:process')->everyMinute()->withoutOverlapping();

That way, even if the previous run is still going, it won't start another instance.

Basically that's it.

The above is the detailed content of Scheduling Artisan Commands and Tasks in Laravel. For more information, please follow other related articles on the PHP Chinese website!