# Changelog of Workflow Heartbeat Monitor - n8n, Make & Cron (`automa-flow/workflow-heartbeat-monitor`) Actor

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

## Changelog

### 2026-09-29: First public release

#### Features

- Record one heartbeat at the final successful step of a workflow, with the success flag, a useful-output count, a duration and a short note.
- Audit up to 500 workflows in one run. Each gets a status: `HEALTHY`, `LATE`, `FAILED`, `ZERO_OUTPUT`, `BELOW_MIN_COUNT`, `NEVER_SEEN` or `INVALID_STATE`, with a reason code.
- Get an email or Slack message only when a workflow needs attention: turn on `problemsOnly` and add an Apify Monitoring alert on the audit Task: Number of results is greater than 0. The audit run itself succeeds. `failRunOnProblem` is an optional alternative that fails the run instead.
- Every run writes a compact `RUN_SUMMARY` with counts, charged events and the next action.

#### Input and billing

- A check-in needs `monitorKey` and `ok`. Leaving either out fails the run and stores nothing, so a misconfigured workflow never looks like a success.
- `mode` can be left out: an input with `monitors` is an audit, anything else is a check-in.
- Invalid keys, counts, silence windows and unknown fields are rejected before a run starts.
- You are not charged for invalid input, a failed read or write, a superseded check-in, or monitors a charge limit stopped before they were judged.

#### Data

- Heartbeats live in your own named key-value store `workflow-heartbeat-monitor`, and an audit never changes them.
- Rows include `source`, `sourceId`, `scrapedAt`, `schemaVersion` and `fingerprint`, so you can keep them as a history as they are.