Laravel scheduled task monitoring

Know when tasks fail
or fall behind schedule.

Laritor is a performance monitoring and issue tracking tool for Laravel. It shows when your scheduled tasks run, whether they succeed, how long they take, and how late they start. Find failing backups, delayed imports, and slow reports, then inspect the recorded events to understand the cause.

Free trial: 300K events · Unlimited apps and users

A task’s schedule, run history, failures, and timingView screenshot
Laritor scheduled task dashboard showing the schedule, last and next run times, successful, failed and skipped runs, success rate, average duration, and average delay
01

Check run outcomesSee successful, failed, and skipped runs.

02

Spot late startsCompare scheduled and actual start times.

03

Improve task performanceInspect the events behind each run.

Delayed scheduled tasks

Find tasks that
start late.

A task can finish successfully and still start later than planned. Laritor shows its scheduled time, actual start time, and how late it was, so you can see which tasks are falling behind.

Look for recurring delays, then check whether earlier tasks, server load, or your scheduler configuration need attention.

Delay and duration measure different things

Delay is how late a task starts.
Duration is how long it takes to run.

Explore task timing and history
Laritor delayed scheduled tasks view showing scheduled times, actual start times, and tasks starting six or nine seconds late

See which tasks started late and by how much.

View screenshot

Schedules and run history

Check what ran.
Find what failed.

A failed scheduled task can leave a backup unfinished or a report unsent. Laritor brings the task’s schedule, status, and recorded runs together so you can check what happened and investigate a specific run.

Explore scheduled task monitoring
01

Check the schedule

See when a task is scheduled to run, when it last ran, and when it should run next. Check that backups, imports, and reports are scheduled as you expect.

02

Review previous runs

See successful, failed, and skipped runs in the task’s history. Filter recorded runs by date, duration, or status to find the one you need to investigate.

03

Understand a failure

Open a failed run to inspect its events. If it threw an exception, view the message, file, line, and stack trace to find where things went wrong.

Scheduled task execution timeline

Understand why a task
slowed down or failed.

For each recorded run, Laritor puts its queries, logs, API calls, and other events in order. Follow the work the task performed, see how long operations took, and inspect the exception when something went wrong.

Explore task run details
The events and exception behind a failed task runView screenshot
Laritor failed scheduled task timeline showing its exception message, N+1 queries, execution duration, start delay, and scheduled, started and completed timestamps
Events recorded with a task run
  • Queries
  • Exceptions
  • Logs
  • API calls
  • Cache
  • Jobs
  • Mail
  • Notifications

Reduce unnecessary queries

Inspect slow or repeated database queries and N+1 query warnings. Use the details to improve queries, batch work, or avoid loading related records one at a time.

Check other services and side effects

Inspect external API calls, cache operations, and dispatched jobs. Follow logs, mail, and notifications to see which steps ran before the task finished or failed.

Read scheduled command output

For scheduled Artisan commands, enable console output recording with the SendOutputToLaritor trait on the command. Read its messages alongside the recorded run.

See output recording setup

Debug with Laritor MCP

Debug task exceptions
with your AI agent.

Connect your AI coding agent to Laritor’s MCP server. Your agent can retrieve an exception’s details, stack trace, and related events, then use that context with your code to investigate a scheduled task failure and implement a fix.

Connect Laritor MCP
An AI agent investigating with Laritor MCPView screenshot
AI coding agent using Laritor MCP to investigate a job exception, trace its related events, and identify the failing code

Example: an agent investigating a job exception with Laritor’s recorded events. Use the same approach to investigate exceptions in scheduled work.

MCP setup guide

Choose what to record

Track problems,
or monitor all activity.

Start with exceptions, include other detected issues, or record all activity to follow task history and performance over time. Each recorded run includes its related events. Choose full observability when you also want to monitor successful runs.

Exceptions only

Record runs that contain an exception, along with the related events that help explain it.

Issues only

Record runs with detected issues, such as exceptions, failed executions, or slow queries, with their related events.

Full observability

Record successful activity too, to follow task run history and monitor performance across your app.

Compare recording modes

Concerned about sensitive information?

Control what you send to Laritor. Filter events and redact passwords, tokens, and personal information before the recorded data leaves your servers.

Explore privacy controls

Install in under 1 minute

Start monitoring
your Laravel scheduled tasks.

Install Laritor’s Laravel package, connect your app, and choose what to record. Investigate task failures, find late starts, and understand what makes scheduled work slow.

Free trial: 300K events · Unlimited apps and users