Did my Sume cron schedule fire? Read last_run_at and next_run_at

Call GET /v1/actions/{action_id} and read two fields: last_run_at, the time the schedule last ran, and cron.next_run_at, the time of the next run. If last_run_at is older than your cadence, check status too, because an inactive schedule does not accept API runs (Scheduled agents).

Fields to check

An API-only schedule has cron: null, so there is no next_run_at to wait for. It runs only when your service calls it.

Confirm with the run list

Page the runs with GET /v1/actions/{id}/runs?limit=20. Each page is { data, has_more, next_cursor }, and limit accepts 1 to 100 with 50 as the default (Scheduled runs).

curl -sS "https://api.sume.com/v1/actions/$ACTION_ID" \
  -H "Authorization: Bearer $SUME_API_KEY" \
  | jq '.data | {status, trigger_type, last_run_at, next: .cron.next_run_at}'

A quick alert rule

Alert when status is not active, or when last_run_at is older than two cadences. Do not alert on the run count alone, because a skipped run on an active schedule is not an error.