Failure signal
An Artisan command throws an exception before completion.
LARAVEL INTEGRATION
Monitor Laravel scheduled tasks with heartbeats
Laravel Scheduler can start commands reliably, but a task can still fail before completing. Send an Upnora heartbeat after the work succeeds and get an alert when the expected execution goes missing.
Job runs↓
Heartbeat sent↓
Upnora receives it✓
GET /h/YOUR_KEY/YOUR_TOKENWHAT CAN FAIL
Why this job can stop silently.
Failure signal
A server or deployment stops running the scheduler.
Failure signal
A dependency fails during a daily report, import or cleanup task.
BASIC INTEGRATION
Send the heartbeat after successful work.
Use the unique GET URL provided by your Upnora dashboard. The examples are generic: replace them with your monitor URL and keep it in an environment variable or secret.
use Illuminate\Support\Facades\Http; Http::timeout(10)->get(config('services.upnora.heartbeat'));IMPLEMENTATION NOTES
Keep the signal meaningful.
Keep the heartbeat URL in .env and expose it through config/services.php. Add the request at the end of the Artisan command, after the report, import or cleanup has completed. The scheduler continues to schedule the command; Upnora only monitors the resulting signal.
See scheduled task monitoring →Common mistake
Do not send the heartbeat before the task or in a finally block. If the command fails, the heartbeat should not be sent.
Wrong: heartbeat → run the job
Better: run the job → heartbeat
MORE HEARTBEAT INTEGRATIONS
Use Upnora with your stack.
FAQ
Laravel heartbeat monitoring, simply explained.
How do I monitor Laravel scheduled tasks?
Create a heartbeat monitor, store its URL in UPNORA_HEARTBEAT_URL, and call that URL after the scheduled command completes successfully.
Can Upnora detect a Laravel task that never started?
Yes. If the expected heartbeat never arrives, the monitor becomes overdue after its interval and grace period.
Should the heartbeat be sent before or after the job?
Send it after the successful work.
ADD A SUCCESS SIGNAL