Cron check-ins

A cron job that fails loudly is easy to find. One that silently doesn't run is not. With check-ins, your job tells SnowAnalytics when it starts and how it ended, and SnowAnalytics watches for the check-in that doesn't come.

A job's first check-in with its schedule creates its monitor. A job that is late, missed or failing fires the A cron job misses its check-in rule in Errors → Alerts, and the alert shows in Recent alerts.

Check in

POST https://api.snowanalytics.app/api/v1/crons/{slug}/checkins

Authenticate with a server key, the same one that sends server errors. Send in_progress when the job starts, then ok with its duration or error with the message.

curl -X POST https://api.snowanalytics.app/api/v1/crons/nightly-invoices/checkins \
  -H "Authorization: Bearer snw_live_your_key" \
  -H "Content-Type: application/json" \
  -d '{ "status": "ok", "durationMs": 1200, "schedule": "0 2 * * *" }'
FieldTypeNotes
statusstringRequired. in_progress, ok or error.
durationMsintegerHow long the run took. When you leave it out, SnowAnalytics uses the time since the last in_progress.
messagestringUp to 500 characters. Shown with a failed run.
schedulestringCreates the monitor on its first check-in.
timezonestringAn IANA time zone, used when the monitor is created.
namestringThe monitor's name, used when the monitor is created.

A good reply is 200 with the monitor's state and when the next check-in is expected:

{ "status": "ok", "monitor": { "slug": "nightly-invoices", "state": "ok", "nextExpectedAt": "2026-11-01T02:00:00.000Z" } }
StatusMeaning
400The slug, the body or the schedule is invalid.
401 / 403The key is missing, invalid, or lacks the events:write scope.
404There is no monitor with that slug, and the check-in carried no schedule to create one.
413The body is over 8 KB.
423Tracking is paused until you upgrade.
429More than 120 check-ins a minute for this key.

A site can have up to 100 monitors.

On this page