# Is warmup actually running?

> Whether Warmerly's warmup workers are alive. A plain authenticated caller gets the derived flag:

Source: https://warmerly.com/docs/warmup/is-warmup-actually-running

```text
GET /warmup/health
```

Whether Warmerly's warmup workers are alive. A plain authenticated caller gets the derived flag:

```json
{ "ok": true, "healthy": true }
```

`healthy` is `true` when the freshest worker heartbeat is under 10 minutes old. It is a platform-level answer, not a statement about your mailboxes: `healthy: true` with nothing sending means the problem is your campaign or mailbox configuration, and [`GET /campaigns/{id}/readiness`](https://warmerly.com/docs/campaigns#readiness-check) will say which. Staff callers additionally get `lastTick` per worker.

`POST /warmup/run` exists but is ops-only: it triggers a planner/dispatcher pass across every workspace on the platform, so it returns `404` for a customer key. Warmup runs continuously on its own; there is nothing to trigger.

## More from Warmup

- [Per-account health and job history](https://warmerly.com/docs/warmup/per-account-health-and-job-history): Two account-scoped endpoints give you the same data filtered to a single mailbox. Both take the account ID…
- [Pause and resume warmup on an account](https://warmerly.com/docs/warmup/pause-and-resume-warmup-on-an-account): Warmup only runs against accounts with status = active or aging. Pausing an account stops it from being…
- [Mailbox health alerts](https://warmerly.com/docs/warmup/mailbox-health-alerts): The last 50 mailbox-health alerts that are still open for your user, newest first. Alerts whose fault has…