Monitoring Netlify Scheduled Functions – including apps built with Bolt

Setup

Set up in three steps

1. Create a heartbeat

   In your account, create a new one under “Heartbeats”, with your function's rhythm and some leeway. You receive a ping address of its own, such as https://runcheck.de/a8k3m2x9q1.

2. The check-in at the end of the function

   This is a Scheduled Function as in the current Netlify documentation; the check-in goes after the work. A five-second time limit leaves enough of the 30 seconds for your work. To test, go to “Cloud compute › Functions”, select the function and click “Run now”.

   // netlify/functions/daily-sync.mts
   import type { Config } from '@netlify/functions';
   
   export default async (req: Request) => {
     // ... your work ...
     await fetch('https://runcheck.de/a8k3m2x9q1', { signal: AbortSignal.timeout(5000) }).catch(() => {});
   };
   
   export const config: Config = {
     schedule: '@daily',
   };

3. Older functions with schedule()

   If your project still uses the older schedule() helper from @netlify/functions, the check-in goes right before the return in the same way:

   import { schedule } from '@netlify/functions';
   
   export const handler = schedule('@daily', async () => {
     // ... your work ...
     await fetch('https://runcheck.de/a8k3m2x9q1', { signal: AbortSignal.timeout(5000) }).catch(() => {});
     return { statusCode: 200 };
   });

The ready-made lines for Linux, PHP, Python, Node.js, n8n, Make, Supabase and Vercel are on the page Cron job monitoring. Your own ping address appears in your account once you create the heartbeat, with the same lines ready to copy.

When something fails

What happens when a run fails

If the function does not start, fails with an error or ends after 30 seconds before reaching the last line, the check-in is missing. After the leeway we alert you; the next successful run brings the all-clear.

FAQ

Common questions about Netlify

My Bolt app is not on Netlify. How do I monitor scheduled tasks then?

On the same principle, on the service where the task runs: call the ping address once at the end of the task. If the app uses Supabase, which Bolt offers as an alternative to its built-in Bolt Database, the guide Monitoring Supabase Cron helps.

What happens when a Netlify Scheduled Function takes longer than 30 seconds?

Then it ends before reaching the last line; the check-in is missing and you hear about it. For longer work Netlify recommends Background Functions; the check-in belongs at their end just the same.

Do Scheduled Functions run in Deploy Previews?

Not on their schedule: according to Netlify, they only run automatically for the published deploy, not for Deploy Previews and branch deploys. You can start them there by hand with “Run now”. Scheduled check-ins therefore only come from production.