Scheduler with cron in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when a Laravel scheduled task is set to run every minute using cron?

Consider this Laravel scheduler code snippet:

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

Assuming the system cron is properly configured to run Laravel's scheduler every minute, what is the expected behavior?

Laravel

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

A The command runs only once when the server starts and never again.

B The 'emails:send' command runs once every minute as expected.

C The command runs every hour instead of every minute.

D The command runs continuously without any delay.

💡 Hint

Think about how Laravel's scheduler and system cron work together.

Laravel's scheduler relies on the system cron to trigger the schedule:run command every minute. The everyMinute() method schedules the task to run each time schedule:run is called, so the command runs once every minute.

📝 Syntax

intermediate

Which Laravel scheduler syntax correctly schedules a task to run daily at 2:30 AM?

Choose the correct Laravel scheduler code to run a command daily at 2:30 AM.

A $schedule->command('backup:run')->dailyAt('2:30 PM');

B $schedule->command('backup:run')->dailyAt('02:30:00');

C $schedule->command('backup:run')->dailyAt('14:30');

D $schedule->command('backup:run')->dailyAt('02:30');

💡 Hint

Check the format Laravel expects for dailyAt() time strings.

Laravel's dailyAt() method expects a string in 'H:i' 24-hour format without seconds. '02:30' is interpreted as 2:30 AM. '02:30:00' includes seconds and is invalid. '14:30' is 2:30 PM, and '2:30 PM' is not a valid format.

🔧 Debug

advanced

Why does this Laravel scheduled command never run?

Given this scheduler code:

$schedule->command('report:generate')->cron('60 * * * *');

Why will the command never execute?

Laravel

$schedule->command('report:generate')->cron('60 * * * *');

A The cron expression '60 * * * *' is invalid because minutes must be 0-59.

B The command name 'report:generate' is incorrect and causes failure.

C The scheduler requires 'everyMinute()' instead of cron expressions.

D The cron expression runs only once a day, so it seems like it never runs.

💡 Hint

Check the valid range for minutes in cron syntax.

Cron expressions require the minute field to be between 0 and 59. '60' is invalid, so the scheduler ignores this task and it never runs.

❓ state_output

advanced

What is the output when a Laravel scheduled task uses 'withoutOverlapping' and the previous task is still running?

Consider this scheduler code:

$schedule->command('sync:data')->everyFiveMinutes()->withoutOverlapping();

If the 'sync:data' command takes 10 minutes to complete, what happens when the scheduler tries to run it again after 5 minutes?

Laravel

$schedule->command('sync:data')->everyFiveMinutes()->withoutOverlapping();

A The second run starts immediately, causing two overlapping processes.

B The scheduler queues the second run to start after the first finishes.

C The second run is skipped because the previous run is still active.

D The scheduler throws an error due to overlapping tasks.

💡 Hint

Think about what 'withoutOverlapping' means in Laravel scheduler.

'withoutOverlapping' prevents a scheduled task from starting if the previous instance is still running. So the second run is skipped to avoid overlap.

🧠 Conceptual

expert

How does Laravel's scheduler interact with system cron to run scheduled tasks?

Which statement best describes how Laravel's task scheduler works with system cron?

A System cron runs the 'schedule:run' command every minute, and Laravel decides which tasks to run based on their schedule.

B Laravel's scheduler replaces system cron and runs tasks independently without cron.

C System cron runs each scheduled task command directly without Laravel's scheduler involvement.

D Laravel's scheduler runs continuously in the background without needing system cron.

💡 Hint

Think about the role of system cron in triggering Laravel's scheduler.

Laravel's scheduler requires system cron to run the 'schedule:run' command every minute. Laravel then checks which tasks are due and runs them. Laravel does not replace cron or run tasks independently.

Practice

1. What is the main purpose of Laravel's scheduler when using cron expressions?

easy

A. To create database migrations automatically

B. To manually execute commands from the terminal

C. To automate running tasks at specified times without manual intervention

D. To generate user authentication scaffolding

Solution

1. Step 1: Understand Laravel scheduler role

   Laravel scheduler automates running tasks like commands or jobs at set times.

2. Step 2: Identify cron usage

   Cron expressions define when tasks run automatically without manual input.

3. Final Answer:

   To automate running tasks at specified times without manual intervention -> Option C

4. Quick Check:

   Scheduler automates tasks [OK]

Hint: Scheduler automates tasks on schedule, not manual commands [OK]

Common Mistakes:

• Confusing scheduler with manual command execution
• Thinking scheduler creates migrations
• Assuming scheduler generates UI code

2. Which of the following is the correct way to schedule a command to run every day at midnight in Laravel's app/Console/Kernel.php?

easy

A. $schedule->command('emails:send')->hourly();

B. $schedule->command('emails:send')->dailyAt('00:00');

C. $schedule->command('emails:send')->cron('0 12 * * *');

D. $schedule->command('emails:send')->everyMinute();

Solution

1. Step 1: Identify daily midnight syntax

   Laravel's dailyAt('00:00') schedules a command at midnight daily.

2. Step 2: Check other options

   everyMinute() runs every minute, cron('0 12 * * *') runs at noon, hourly() runs every hour.

3. Final Answer:

   $schedule->command('emails:send')->dailyAt('00:00'); -> Option B

4. Quick Check:

   dailyAt('00:00') = midnight daily [OK]

Hint: dailyAt('00:00') means every day at midnight [OK]

Common Mistakes:

• Using cron('0 12 * * *') which runs at noon, not midnight
• Confusing everyMinute() with daily scheduling
• Using hourly() instead of dailyAt()

3. Given this scheduler code in app/Console/Kernel.php:

$schedule->command('backup:run')->cron('0 3 * * 1');

When will the backup:run command execute?

medium

A. Every hour on the hour

B. Every day at 3:00 AM

C. Every Sunday at 3:00 AM

D. Every Monday at 3:00 AM

Solution

1. Step 1: Decode cron expression '0 3 * * 1'

   The fields mean: minute=0, hour=3, day=any, month=any, weekday=1 (Monday).

2. Step 2: Interpret execution time

   The command runs at 3:00 AM every Monday.

3. Final Answer:

   Every Monday at 3:00 AM -> Option D

4. Quick Check:

   cron('0 3 * * 1') = Monday 3AM [OK]

Hint: Cron weekday 1 means Monday at specified time [OK]

Common Mistakes:

• Confusing weekday 1 with Sunday
• Assuming it runs daily instead of weekly
• Misreading hour or minute fields

4. You wrote this in app/Console/Kernel.php:

$schedule->command('report:generate')->cron('60 * * * *');

What is the problem with this cron expression?

medium

A. Minute value 60 is invalid; minutes range from 0 to 59

B. Hour value is missing

C. Day of month is invalid

D. Cron expression is missing the command name

Solution

1. Step 1: Check cron minute field

   The first field is minute; valid values are 0 to 59. 60 is invalid.

2. Step 2: Confirm other fields

   Other fields are valid, but minute 60 causes syntax error.

3. Final Answer:

   Minute value 60 is invalid; minutes range from 0 to 59 -> Option A

4. Quick Check:

   Minute must be 0-59, 60 is invalid [OK]

Hint: Minutes in cron go 0-59, never 60 [OK]

Common Mistakes:

• Using 60 as minute value
• Ignoring cron field ranges
• Assuming missing hour causes error here

5. You want to schedule a Laravel command to run every weekday at 6:30 PM but only if a certain feature flag is enabled. Which is the best way to implement this in app/Console/Kernel.php?

hard

A. Use if (config('features.enable_task')) { $schedule->command('task:run')->weekdays()->at('18:30'); }

B. Schedule the command daily at 18:30 without condition

C. Use cron expression '30 18 * * 0-6' to run every day

D. Add the condition inside the command handle method instead of scheduler

Solution

1. Step 1: Understand conditional scheduling

   Laravel scheduler allows conditional scheduling by wrapping schedule calls in if statements.

2. Step 2: Use weekdays() and at() methods

   weekdays() limits to Monday-Friday, at('18:30') sets time to 6:30 PM.

3. Step 3: Apply feature flag condition

   Check config('features.enable_task') before scheduling to enable/disable task.

4. Final Answer:

   Use if (config('features.enable_task')) { $schedule->command('task:run')->weekdays()->at('18:30'); } -> Option A

5. Quick Check:

   Conditional scheduling with if + weekdays() + at() [OK]

Hint: Wrap schedule call in if to conditionally enable task [OK]

Common Mistakes:

• Scheduling unconditionally ignoring feature flag
• Using wrong cron for weekdays
• Putting condition inside command instead of scheduler