Know when a job fails, or never runs

Wrap a cron job, queue worker or scheduled task once. Vigilon records every run as a trace, groups its failures with your other errors, and marks the job overdue when it misses its schedule. For Node.js and Python.

What you get

Every run, its result and its trace.

A trace for every run

Each run is recorded with its own trace, even when a web request starts it, with the database queries and outgoing calls it made. Job run traces are always kept.

Overdue when runs are missed

Give a job its cron schedule and Vigilon marks it Overdue once two expected runs have passed without a completed one.

Failures become error groups

A run that throws is grouped with your other errors by job and message, so the first failure of a new kind emails your team.

Health at a glance

The Jobs page shows each job as Healthy, Failing or Overdue, with its schedule, last run, number of runs, failures and run duration.

Cron, queues and intervals

Wrap a node-cron task, a BullMQ processor, a setInterval loop, a Celery task or any function that does one unit of work. Each attempt of a queued job is its own run.

Emails for missed runs on Team and Pro

Automatic insights email your team when a scheduled job misses two runs, or keeps failing for five runs in a row or a full day. Missed-run emails cover jobs scheduled at least ten minutes apart, once three of their runs are on record.

How it works

Wrap the job once, Vigilon does the rest.

  1. 01

    Start the SDK, then wrap one run

    With the SDK running, put withJobMonitor in Node.js or with_job_monitor in Python around the work one run does, and give the job a stable name.

  2. 02

    Add its schedule

    Pass the job's cron expression as schedule. It runs nothing; Vigilon only uses it to know when a run is due.

  3. 03

    See every run

    Runs show up on the Jobs page with their status, duration and trace, next to the requests your app serves.

  4. 04

    Hear about problems

    A new kind of failure emails your team on every plan. A job that stops running is marked Overdue, and on Team and Pro an insight emails you if its runs are at least ten minutes apart.

Setup

One wrapper around each job.

Start the SDK first, as in the Node.js or Python quickstart: the wrapper reports through it, and without it a job runs as normal but reports nothing. Then wrap each job, since jobs are not detected on their own. Errors that leave the job are recorded and thrown again, so your retries still work.

Docs Node.js quickstartPython quickstartNode.js jobsPython jobsNestJS scheduled tasks

// Start the process with: node --import @vigilon/node/register jobs.js
import { withJobMonitor } from "@vigilon/node";
import cron from "node-cron";

cron.schedule("0 3 * * *", () =>
  withJobMonitor({ name: "sync-users", schedule: "0 3 * * *" }, async () => {
    await syncUsers();
  }),
);

Start the process with node --import @vigilon/node/register, as in the quickstart. Use the same name on every run; a name per item creates a new job each time. The cron expression is read in UTC.

Compared with Sentry

Job monitoring in Vigilon and Sentry.

Sentry monitors scheduled jobs with cron monitors. This is how the two compare, with a source for every Sentry fact.

CapabilitySentryVigilon
Scheduled job and queue worker monitoringCRON MONITORS1 included on every plan, more at extra cost [1]YESEvery run is a trace; missed runs flagged from your cron schedule
Which traces are keptYOUR SAMPLE RATESet in the SDK; the guide says to lower it in production [9]AFTER THE FACTEvery background job trace. For HTTP requests Vigilon handles filtering for you.
Slack, PagerDuty and issue-tracker alertsYESSlack, PagerDuty, Microsoft Teams, Jira and more [6]NOT YETEmail only today
  1. [1] Sentry pricing: spans, logs and cron monitors included on each plan: sentry.io/pricing. Checked 2026-10-25.
  2. [6] Sentry integrations: docs.sentry.io/organization/integrations. Checked 2026-10-25.
  3. [9] Sentry Express setup guide: docs.sentry.io/platforms/javascript/guides/express. Checked 2026-10-25.

Read the full Vigilon and Sentry comparison

Questions

Cron job monitoring questions.

What is cron job monitoring?

Cron job monitoring checks that scheduled jobs run when they should and finish without errors. Vigilon records every run of a wrapped job as a trace, groups failed runs into error groups, and marks a job Overdue when its cron schedule says runs were missed.

How does Vigilon know a job missed a run?

From the cron expression you pass as schedule, read in UTC. A job is Overdue once its schedule has expected two runs since its last completed run and neither arrived. A job whose last run failed shows as Failing instead.

Do I get an email when a job stops running?

On Team and Pro, yes, for jobs scheduled at least ten minutes apart once three of their runs are on record: an automatic insight emails your team after two missed runs. A job that runs more often still shows as Overdue on the Jobs page, on every plan, without that email. A failed run emails your team the first time a new error appears.

Does it work with BullMQ and Celery?

Yes. Wrap the BullMQ processor and each attempt becomes its own run, with its Redis calls in the trace. For Celery, start Vigilon in each worker process and wrap the task with with_job_monitor; Vigilon does not trace Celery tasks on its own.

Do I need a heartbeat URL to ping?

No. The wrapper reports each run through the same SDK that monitors your app, so a job's runs, errors and traces sit next to your requests, with no URL to call.

Which plans include job monitoring?

Every plan monitors jobs and counts each run, retries included, against its job run quota. Emails for missed runs and failure streaks come with automatic insights, on Team and Pro.

Get started

Start free for two months.

Pick a plan, add the SDK, and Vigilon starts watching your app. Starter is free for your first two months, with no card needed.