Render Cron Job Monitoring
Render Cron Jobs run a command on a schedule — but if the command fails or the schedule silently stops firing, you find out when something downstream breaks. crond.io watches the schedule and alerts you the moment a run is late or fails. It's one curl.
How it works
Create a crond.io monitor with the same schedule as your Render Cron Job (Render cron schedules are UTC). Ping crond.io when the command finishes; if the ping never arrives, or you report a failure, crond.io alerts you.
Quick: ping on success
The simplest setup — append a ping to your Cron Job's command so it only fires when the job succeeds:
./run-job.sh && curl -fsS "https://api.crond.io/ping/$CROND_PING_KEY"
Full: start, success, and failure
For run duration and instant failure alerts, wrap the job in a small script and set it as the Cron Job command:
#!/usr/bin/env bash PING="https://api.crond.io/ping/$CROND_PING_KEY" curl -fsS -X POST "$PING/start" # job started if ./run-job.sh; then curl -fsS "$PING" # success else curl -fsS -X POST "$PING/fail" # failure -> instant alert exit 1 fi
Set the ping key
In your Render service's Environment, add CROND_PING_KEY with the ping key from your crond.io monitor. Keeping it in an environment variable means the key never lands in your repo.
That's it
Your Render Cron Job now reports every run. Miss one — because the job crashed or the schedule stalled — and crond.io alerts you instead of leaving a silent gap.