Heartbeat pings
Prove ongoing work is alive.
- Completion pings over GET or POST
- Timer starts after the first successful ping
- Missed windows open evidence-linked incidents
Best for workers, queues, and daemons.
Proof that scheduled work completed.
A control tower for recurring jobs and service health. Explore one failed monitored run from its first signal through attached evidence, incident routing, alert delivery, and an optional customer-safe status update.
Replay one failed run from signal to public proof.
Nightly invoice sync
Interactive run proof / finance:invoices:sync
Running
Captured
Failed
Delivered
Complete
02:00:01 UTC
Signal received
The scheduled command identified the run before LatidoFlow assumed any outcome.
- Source
- Laravel scheduler
- Schedule
- 0 2 * * *
- Environment
- Production
Attached evidence
Sensitive values redacted
01 run accepted: finance:invoices:sync 02 source: laravel-scheduler 03 schedule: 0 2 * * * 04 environment: production 01 Processing 1,248 invoices 02 Stripe API response 429 03 Retrying in 30s (attempt 3/3) 04 App\Jobs\SyncInvoice.php:214 01 exit_code: 1 02 duration_ms: 13042 03 incident: opened 04 reason: retry budget exhausted 01 channel: incident webhook 02 provider response: 202 Accepted 03 delivery status: delivered 04 delivered_at: 02:00:15 01 public impact: degraded 02 update published: 02:00:20 03 sensitive context: redacted 04 proof chain: complete Two signals. Two different operational truths.
A heartbeat proves that recurring work checked in. An uptime check proves that an endpoint returned the expected response. LatidoFlow keeps those contracts separate so a green state means something precise.
Uptime checks
Prove endpoints are reachable.
- HTTP GET checks against one configured URL
- Optional encrypted request header
- Exact expected status verification (200 by default)
Best for services, APIs, and websites.
Define the monitor. Then prove the runtime.
The API synchronizes the monitor contract. Verification confirms the connection. A real heartbeat or lifecycle event is still required before the run has execution proof.
Read the API contract
1. Sync monitor definitions
REST / any HTTP client
curl -X POST https://your-host.example/api/v1/monitors/sync
Authorization: Bearer LATIDOFLOW_TOKEN
Content-Type: application/json
project: { name: App, slug: app }
environment: { name: Production, slug: production }
monitors: [{ name: Nightly sync, type: heartbeat, metadata: { source: laravel-scheduler, source_kind: scheduled } }]
2. Verify the connection
Laravel command
$ php artisan latidoflow:verify
Token and definition sync verified.
Execution proof still requires a real heartbeat or lifecycle event.
Publish customer-safe proof without publishing internal evidence.
Status pages turn operational incidents into clear customer updates while internal logs, tokens, and sensitive execution context stay out of the public view.
- Customer-safe incident history
- Evidence-linked updates
- Public or password-protected access
- Explicit incident timelines
Demo Workspace status
Customer-facing incident update
Invoice processing is delayed
The scheduled invoice sync did not complete. The team has been alerted and is investigating.
Updated at 02:00 UTC / Internal output redacted
Stop guessing. Start proving.
Know when recurring work completed—and when it did not—with the evidence needed for the next action.