Monitor Laravel scheduled tasks after the work completes.

Laravel’s scheduler selects due tasks. A queued task may complete later in a worker, and a background command may outlive the scheduler invocation. Place the heartbeat at the end of the work whose result matters.

Use a separate monitor if you also want evidence that the host invokes the scheduler. That monitor cannot stand in for every scheduled task.

Setup

Instrument a scheduled command’s actual workload

Example command handler. Store the URL in config/services.php using your deployment secret and replace the workload method.

In this example, performRequiredWork must throw on failure. If your workload returns a status instead, check it and return a failure exit code before reaching the heartbeat. For queued work, use this pattern inside the queue worker’s successful processing path. Keep URLs out of source control and error logs. Review how your application handles exceptions and returns exit codes.

Real-world examples

// services.php: 'pingcron' => ['url' => env('PINGCRON_URL')],
public function handle(): int
{
    $this->performRequiredWork(); // This method must throw if required work fails.

    // Report only after all required work succeeds.
    try {
        \Illuminate\Support\Facades\Http::timeout(10)
            ->get(config('services.pingcron.url'))->throw();
    } catch (\Throwable $error) {
        // Record telemetry failure without logging the private URL.
        \Illuminate\Support\Facades\Log::warning('Heartbeat delivery failed');
    }

    return self::SUCCESS;
}

What Laravel scheduled tasks should you monitor?

Anything in app/Console/Kernel.php that has to run.

Alerts where you'll actually see them.

Save alert destinations for the owning account. Email, Slack, and Discord are included on every plan; custom webhooks require Pro or above.