Reproducible technical scenario

The deployment finished. The expected scheduled task never reported again.

A healthy application can keep serving requests while its scheduler is absent. This automated product proof distinguishes a missed occurrence from an explicit Laravel schedule skip, and never invents a successful run for either one.

Last reviewed: August 1, 2026

Lab evidence, not a customer story or root-cause claim

The deployment window is the setup for this controlled scenario. The proof establishes missing-run behavior; it does not claim that a real deployment caused a customer scheduler failure.

Direct answer

An armed occurrence that never arrives becomes a public outage.

After the monitor has received its first successful execution signal, LatidoFlow has evidence from which to arm the next expected window. It waits through the configured due time and grace period.

If no matching run or explicit skip arrives, evaluation opens a missing_run incident, marks the monitor failed, and changes the linked component and overall page to major outage.

If Laravel reports that schedule filters, overlap protection, or another supported condition explicitly skipped the occurrence, LatidoFlow advances the expected window and records skip provenance without creating a fake successful run.

No execution evidence

The occurrence disappears.

1. Expected: the previous valid signal arms the next due time.
2. Overdue: due time and grace pass with no run or skip evidence.
3. Incident: one missing-run occurrence opens and linked public status becomes unavailable.

Explicit lifecycle evidence

Laravel reports a deliberate skip.

1. Identified: the skip uses the scheduled task's stable monitor identity.
2. Preserved: skip reason and idempotency evidence remain attached to the monitor.
3. Advanced: the expected window moves forward without fabricating a successful run.

What this proves

A missing expected occurrence opens a distinct incident after its grace period.
The monitor, linked component, and overall public status page agree on the outage.
An explicit skip is idempotent and advances the schedule window.
A skip is not stored as a successful execution.
Missed work and deliberately skipped work remain distinguishable.

Current boundary

The heartbeat timer arms after the first successful signal; a definition alone is not execution proof.
Safely named Laravel 13 scheduled tasks can report automatically. Unnamed schedules remain waiting definitions and do not report automatically.
The scenario detects absence; it does not identify deployment as the root cause or repair the scheduler.
Monitoring the scheduler and evaluator pipeline is a separate operational-health responsibility.
No customer incident frequency or detection-time result is claimed.

Continue through expected-run monitoring

Laravel cron monitoring Review named schedule discovery, expected windows, and skip evidence. Cron job monitoring See the framework-neutral heartbeat and grace-period contract. Queued but never started Contrast a missing schedule occurrence with a known run waiting for a worker.

Make the next expected run explicit.

Start with one named Laravel schedule or heartbeat. Once real execution evidence arms the monitor, LatidoFlow can distinguish silence from a deliberate skip.

Create a workspace Read the Laravel guide