Built for production Laravel apps
Crontinel is most valuable when your background jobs are load-bearing: billing, data sync, reporting, communication. Here are all 77 use cases.
Cache and Optimize
bootstrap/cache/routes-v7.php Explained — Laravel Route Cache Monitoring
What is bootstrap/cache/routes-v7.php? Learn how Laravel route:cache creates it, what can go wrong during rolling deploys, and how to get alerted when the cache is stale or missing.
How to Monitor php artisan event:cache in Production
Monitor Laravel event:cache in production so you catch missing listeners, stale event maps, and silent registration failures before customers do.
How to Monitor php artisan model:prune in Production
Monitor Laravel model:prune in production so you catch missed pruning runs, skipped models, and silent cleanup failures before old data fills the database.
How to Monitor php artisan notifications:prune in Production
Monitor Laravel notifications:prune in production so you catch missed runs, slow executions, and silent failures before the notifications table balloons.
How to Monitor php artisan optimize in Production
Monitor Laravel's optimize command in production so you catch config cache failures, route cache problems, and bootstrap errors before they break deploys.
How to Monitor php artisan optimize:clear After Deployment
Make php artisan optimize:clear visible after Laravel deployments so stale config, route, view, and event cache problems do not survive unnoticed.
Monitoring config:cache in Laravel Production
Watch Laravel's config:cache command in production so stale environment values, broken config files, and missed deploy hooks do not quietly break your app.
Monitoring config:clear in Laravel Production
Watch Laravel's config:clear command in production so an accidentally cleared config cache, a failed rebuild, or a half-finished deploy step does not leave your app running without cached configuration.
Monitoring event:clear in Laravel Production
Watch Laravel's event:clear command in production so an accidentally cleared event cache, a missed rebuild after deploy, or a half-finished deploy step does not leave your app running without cached event discovery.
Monitoring route:clear in Laravel Production
Watch Laravel's route:clear command in production so a cleared route cache does not leave old routes, missing endpoints, or a half-finished deployment unnoticed.
Monitoring view:cache in Laravel Production
Monitor Laravel's view:cache command in production so stale compiled views, missing templates, and permission errors do not silently break your deployed application.
Monitoring view:clear in Laravel Production
Monitor Laravel's view:clear command in production so stale compiled views from a previous release are reliably removed before the new cache is built.
Scout and Telescope
Clearing and Monitoring Laravel Telescope Entries
Telescope entry missing after a job ran? It's not always a bug in your code — clear vs prune behavior and silent capture failures explained.
Detect When Laravel scout:import Fails to Import All Records
Monitor Laravel Scout's scout:import command in production so you catch partial imports, memory exhaustion, and silent queue failures before search goes stale.
Detect When Laravel scout:sync-index-settings Fails in Production
Monitor Laravel Scout's scout:sync-index-settings command so you catch invalid config pushes, engine API rejections, and partial settings syncs before search relevance degrades.
Monitoring Laravel Telescope Prune in Production
Learn how php artisan telescope:prune works, why it fails silently, and how to detect when your Telescope data cleanup is not running.
Monitoring scout:flush in Laravel Production
Track when Laravel Scout's scout:flush command runs in production to prevent accidental index wipes, catch deployment errors, and recover search data faster.
Cron and Scheduler
Cron Heartbeat Monitoring for Laravel Schedulers
Use cron heartbeat monitoring to catch the moment schedule:run stops arriving, runs late, or silently skips a scheduled task in production.
How to Detect When Laravel schedule:interrupt Fails After Deployment
Learn how to detect when php artisan schedule:interrupt fails to stop stale schedule:run processes after deployment, preventing old code from running in production.
How to Monitor php artisan schedule:run in Production
Monitor Laravel's schedule:run command in production so you catch missed executions, slow runs, and silent scheduler failures before the missed jobs pile up.
Laravel Cron Monitoring for Scheduled Tasks, Missed Runs, and Failures
Monitor every Laravel scheduled task in production so you catch missed runs, non-zero exits, and silent scheduler outages without instrumenting each task individually.
Monitoring GitHub Actions Scheduled Workflows: Detect When Scheduled Runs Go Silent
GitHub Actions scheduled workflows can silently stop triggering. Learn how to monitor cron-based workflows, detect missed runs, and alert before your team notices gaps.
Monitoring php artisan schedule:work in Laravel Production
Monitor Laravel's schedule:work daemon in production so you catch process crashes, memory leaks, and silent failures before your scheduled tasks stop running.
Setting Up spatie/laravel-schedule-monitor in Production
How to install, configure, and run spatie/laravel-schedule-monitor in a real Laravel production environment. Covers database setup, event listeners, monitoring missed schedules, and pairing it with Crontinel for alerting.
Horizon and Workers
Detect When Laravel Horizon Workers Are Running But Not Processing Jobs
Your Horizon dashboard shows active supervisors and workers, but jobs sit in the queue for minutes. Here is how to catch worker starvation before it turns into a production incident.
horizon:purge Not Cleaning Jobs? Detect Silent Failures
horizon:purge can exit with code 0 while Redis memory keeps climbing. Here is exactly how to tell if it is actually working — and how to get alerted when it isn't.
Laravel Horizon Monitoring for Paused Supervisors, Queue Depth, and Failed Jobs
Monitor Laravel Horizon in production so you catch paused supervisors, queue backlogs, and failed-job spikes without staring at the dashboard manually.
Monitor php artisan horizon:stale-process-cleanup in Production
Laravel Horizon workers can accumulate stale processes over time, consuming memory and preventing clean restarts. Here's how to detect when your stale-process cleanup fails and what to do about it.
Monitoring horizon:continue in Laravel Production
Monitor Laravel's horizon:continue command in production with instant alerts for failures, slow execution, and unexpected exits.
Monitoring horizon:pause in Laravel Production
Monitor Laravel's horizon:pause command in production with instant alerts, failure detection, and schedule tracking to keep your Horizon queues healthy.
Monitoring horizon:terminate in Laravel Production
Monitor Laravel's horizon:terminate command in production with instant alerts, log tracking, and failure detection using Crontinel.
Monitoring horizon:work in Laravel Production
Monitor horizon:work in Laravel production with real-time alerts, failure tracking, and detailed logs to keep your queue workers running smoothly.
Database and Migrations
Detect When Laravel migrate:fresh Runs in Production
A production migrate:fresh drops every table. Here's how to monitor for accidental destructive database commands and get alerted before you lose data.
Detect When php artisan migrate:rollback Fails in Production
Rolling back migrations in production is risky. Here's how to monitor migrate:rollback for partial failures, stuck batches, and accidental rollbacks before they corrupt your database.
How to Monitor php artisan migrate in Production
Monitor Laravel migrate runs in production so you catch failures, long-running schema changes, and rollback problems before they take your site down or corrupt data.
Monitoring Spatie Laravel-Backup in Production
Get alerted when laravel-backup fails, backup:run exits without completing, or your scheduled database backups silently stop. Covers Spatie laravel-backup monitoring patterns for Laravel production teams.
Other
Detect When php artisan db:wipe Runs in Production
php artisan db:wipe drops every table without running migrations back. Here's how to monitor for accidental db:wipe commands and recover before your production app is down for hours.
How to Debug a Laravel Cron Job That Fails With No Log Output
Your Laravel cron job shows FAIL but there's nothing in the log. Here's how to find the real error, from output redirection gotchas to missing env vars and silent exceptions.
How to Monitor Laravel cache:prune-stale-tags in Production
Monitor Laravel's cache:prune-stale-tags command so stale tagged cache metadata does not build up silently when the scheduler, cache driver, or cron job fails.
How to Monitor Laravel Reverb Server in Production
Laravel Reverb is a long-lived WebSocket server that can crash or stop without you noticing. Here is how to detect when Reverb goes down, set up health checks, and get alerted before your users do.
How to Monitor sanctum:prune-expired and Fix Expired Token Cleanup in Laravel
Monitor sanctum:prune-expired in production so you catch missed cleanup runs and silent failures before expired tokens bloat your personal_access_tokens table.
Monitor php artisan passport:purge in Laravel Production
passport:purge cleans expired tokens, but when it fails your auth database grows unbounded — slowing queries and risking memory pressure. Here is how to detect purge failures before they degrade API performance.
Monitoring Laravel Forge Cron Jobs in Production
Laravel Forge schedules your cron entries and restarts daemons, but silent schedule failures still slip through. Here's how to monitor Forge cron jobs, catch missed runs, and alert before customers notice.
Monitoring Laravel Vapor Cron Jobs in Production
Laravel Vapor runs scheduled tasks through Lambda, not traditional cron. Here's how to monitor them, catch silent failures, and avoid the gaps that Vapor's architecture creates.
Monitoring php artisan db:seed in Laravel Production
Detect when php artisan db:seed silently fails in production because of the --force prompt, missing autoload, or model validation errors. Covers monitoring database seeding in Laravel production environments.
Monitoring php artisan pennant:purge in Laravel Production
php artisan pennant:purge removes stale feature flag data from the cache. When it stops running, feature flag storage grows unbounded and old flags may affect unrelated deployments. Here is how to monitor it and catch failures before they cause production issues.
Monitoring Prometheus Metrics in Laravel Production
Laravel apps that expose Prometheus metrics often miss cron and queue failures. Here is how to pair Prometheus with targeted cron monitoring so nothing slips through the gaps.
Backup and Storage
Detecting When Laravel backup:clean Fails to Run
Find out when php artisan backup:clean silently skips cleanup and old backups start filling your disk. Get alerted before storage costs spiral.
Monitoring backup:run Failures in Laravel Production
Detect when php artisan backup:run silently fails in production. Learn what causes backup command failures and how to get alerted before data loss.
Monitoring Laravel Backup Health Checks in Production
Learn how php artisan backup:monitor works, what backup health issues it catches, and how to get alerted when your Laravel backups are unhealthy.
Monitoring storage:link in Laravel Production
Monitor Laravel's storage:link command in deployment so you know the public symlink was created and your user uploads are reachable before traffic arrives.
Queue Monitoring
How to Monitor php artisan cache:clear Cron Job Failures
Monitor php artisan cache:clear cron jobs in production so you catch missed runs, non-zero exits, and stale cache before users see the breakage.
How to Monitor php artisan queue:failed in Production
Monitor Laravel queue:failed in production so you catch new failures, repeated job errors, and silent accumulation before users report it.
How to Monitor php artisan queue:flush in Production
Monitor Laravel's queue:flush command in production. Get alerts when failed jobs are purged unexpectedly or on an unapproved schedule.
How to Monitor php artisan queue:forget in Production
Monitor Laravel's queue:forget command in production. Get alerts when failed jobs are manually removed and their diagnostics disappear before review.
How to Monitor php artisan queue:monitor in Production
Monitor Laravel queue:monitor in production so you catch backed-up queues, QueueBusy events, and scheduler failures before the backlog turns into an incident.
How to Monitor php artisan queue:restart in Production
Monitor Laravel queue:restart in production so you catch workers that never come back, cache mismatches, and silent queue stalls after deploys.
How to Monitor php artisan queue:retry in Production
Monitor Laravel's queue:retry command in production. Get alerts when retry storms, repeated failures, or bad batches make recovery worse.
How to Monitor php artisan queue:work in Production
Monitor Laravel queue:work in production so you catch crashed workers, stale deploys, and memory leaks before your jobs start piling up.
How to Set Up Laravel Queue Monitoring in Production: Step-by-Step Guide
A practical step-by-step guide to setting up queue monitoring in Laravel production, from choosing a queue driver to configuring Supervisor, tracking queue depth, and adding external heartbeat monitoring.
Laravel Queue Monitoring: Depth, Failures, and Stuck Jobs
Monitor Laravel queues in production. Alert on queue depth, failed job spikes, and oldest job age before customers notice slow background processing.
Laravel Queue Worker Timeout Monitoring
Monitor Laravel queue worker timeouts, hanging jobs, and stale workers before your queue backs up. Crontinel catches timeout patterns after deploys and slow downstream calls.
Monitor Laravel Queue Processing Time — Detect When Jobs Run Slow
Laravel queue workers are running but jobs take longer than expected. Here's how to detect queue latency degradation before it becomes an outage.
Monitoring Failed Job Retry Loops in Laravel Horizon
A job that fails and retries forever burns queue workers without progress. Crontinel detects rising failed job rates and oldest job age spikes before the retry loop fills your queue.
Monitoring Redis Queue Performance in Laravel Production
Redis-backed queues degrade silently — latency creeps up, throughput drops, and jobs pile up before anyone notices. Here's how to detect Redis queue performance issues before they become incidents.
Monitoring Supervisor Queue Worker Config in Laravel Production
A production-ready Supervisor config for Laravel queue workers, the settings that silently break processing, and how to detect misconfigured workers before the backlog explodes.
Alerting and Incident Response
Incident Alert System for Laravel Cron and Queue Failures
Route Laravel incident alerts to the right place with Slack, PagerDuty, and webhooks when cron jobs, queue workers, or scheduled tasks break.
Production Cron Job Alerting for Laravel: Get Notified When Schedules Break
Set up reliable cron job alerting for Laravel production apps. Know immediately when a scheduled task fails, runs late, or stops running entirely.
Webhook Monitoring for Laravel and API Teams
Monitor webhook delivery failures, retries, and stalled callback queues before customers notice. Crontinel turns webhook jobs into visible incidents instead of silent breaks.
Status Pages
Laravel Status Page for Cron and Queue Incidents
Show customers and teammates when cron jobs, queue workers, or webhook delivery is delayed. Crontinel makes it easy to publish a Laravel status page for incidents that matter.
Open Source and Self-Hosted Status Page for Laravel Incidents
Build an open source or self hosted status page for Laravel cron, queue, and webhook incidents without relying on a third-party status vendor.
Pulse
Monitor Laravel Pulse Health in Production
Your Pulse dashboard shows data from yesterday and you don't realize it until someone asks why the failed jobs graph flatlined. Here is how to catch Pulse outages before they cost you a morning of debugging.
Monitor Laravel pulse:restart in Production
pulse:restart runs silently during deploys and fails silently too. If the new Pulse worker cannot start, you won't know until someone notices the dashboard froze. Here is how to catch restart failures before they cost you Pulse data.
Multi-Tenant and Teams
Monitoring Background Jobs in a Multi-Tenant Laravel Application
In a multi-tenant Laravel app, a job failure for one tenant can cascade to others. Crontinel monitors queue depth and failed job rates so you catch tenant-specific failures before they spread.
Multi-Tenant Job Monitoring for Laravel: One Dashboard for All Your Apps
Monitor background jobs across multiple Laravel applications from a single dashboard. Separate API keys, per-app thresholds, and team access for multi-app Laravel teams.
SaaS Background Job Monitoring for Laravel Applications
Revenue-critical background jobs need dedicated monitoring. Invoice generation, subscription renewals, and webhook delivery can fail silently. Crontinel surfaces failures before customers notice.
Deploy and CI/CD
Start in two commands
No account needed. Crontinel works locally and in production from day one.