# Changelog of Apify Missed Schedule Monitor (`automa-flow/apify-missed-schedule-monitor`) Actor

- **URL**: https://apify.com/automa-flow/apify-missed-schedule-monitor/changelog.md
- **Full Actor documentation**: https://apify.com/automa-flow/apify-missed-schedule-monitor.md

## Changelog

### 2026-10-05: First release

#### Features

- Check your Apify schedules through the API and get one row per schedule: on time, running, late, skipped because an exclusive schedule's previous run was still active, failed, disabled or truly missing.
- Leave **Schedule IDs** empty to check every schedule your token can see, or list the ones you care about.
- Each schedule keeps its own checkpoint, so a scheduled check continues where the last one stopped, up to 24 hours back.
- A run that is still in progress is rechecked until it finishes, and a miss that turns into a late run within six hours is updated to `LATE_START`.
- `new_incidents` marks problems found for the first time, so an alert fires once.
- Leave the token empty to see a labeled sample (`DEMO_SCHEDULE_CHECK`). A saved Task with an empty token fails as `AUTH_MISSING` instead, so a monitor never runs on sample data.

#### Reliability

- A slot is matched by the run's own scheduler metadata, never by start time alone. Because the run list leaves that metadata empty, the Actor reads only the run details that can decide a selected slot.
- A miss or an overlap skip is confirmed by the schedule's own log, where Apify records that it skipped the start or could not start it.
- When the data cannot prove a miss (daylight-saving edge, config edit, short history, unreadable run, a token that cannot read the schedule log), the slot is reported as unverifiable instead of missing, and it is not charged.
- One unreadable schedule or run does not fail the other schedules. A failed read never overwrites the last good state.
- A rejected token, a token without read access and a changed API contract fail the run with a clear reason in `RUN_SUMMARY`; a refused read is named in the message.

#### Pricing

- $0.0005 per run, plus $0.001 per schedule whose check finalized an expected run that no earlier check reported. Disabled schedules, schedules with nothing due, rechecked slots, the demo, retries and unreadable schedules are free.
- A charge limit is spent only on schedules that are charged. Schedules past the limit are `OMITTED` and checked on the next run.