Heartbeat Monitors
Regular cron jobs check if a URL responds. Heartbeat monitors work in reverse — your bot pings QuzenixCron, and if it goes silent, we alert you. Available on Pro and Business plans.
How it works
Each heartbeat monitor has a unique ping URL. Your bot or service hits that URL at a regular interval (e.g. every 5 minutes). QuzenixCron tracks the last ping time. If more thaninterval + grace period passes without a ping, an alert fires.
This catches failures that a regular cron job can't — like a bot process that crashes, a server that runs out of memory, or a deployment that silently stops executing.
Setup
Go to Settings → Heartbeat Monitors and create a new monitor. Set the expected interval (how often your bot pings) and the grace period (extra buffer before an alert fires). Copy the ping URL.
Sending a ping
Hit the ping URL with a GET or POST request — no authentication needed. Call it from wherever your bot runs.
# Shell / cron
curl https://quzenixcron.com/api/ping/YOUR_TOKEN
# Python
import requests
requests.get("https://quzenixcron.com/api/ping/YOUR_TOKEN")
# Node.js
fetch("https://quzenixcron.com/api/ping/YOUR_TOKEN")A successful ping returns { "ok": true, "received_at": "..." }.
Telegram bot example
Add a ping call to your bot's main loop or polling handler so it fires every time the bot processes an update:
# Python (python-telegram-bot)
import requests
async def on_message(update, context):
# your bot logic...
# ping heartbeat at the end of every handler
requests.get("https://quzenixcron.com/api/ping/YOUR_TOKEN", timeout=3)Alert behavior
When a monitor goes silent past its window, QuzenixCron sends an alert via:
Email — all plans. Telegram, Slack, Discord — Pro and Business only, if connected in Settings.
Alerts have a 1-hour cooldown per monitor to prevent spam. When a new ping arrives after a silent period, the cooldown resets — so the next down-cycle alerts fresh.
Plan limits
Pro plans include 5 heartbeat monitors. Business plans include 20. Free plans cannot create heartbeat monitors.