Docs › APScheduler and other in-process schedulers with RunVouch

APScheduler and other in-process schedulers with RunVouch

APScheduler, node-cron and node-schedule run inside your application process. When that process is restarted at the wrong moment, crashes or is scaled to zero, the schedule goes with it and nothing outside knows.

How it runs on APScheduler (in-process)

Inside the scheduled function with the Python or Node client. The agent's cadence is what makes the missing process visible.

Store the key

An environment variable on the process.

Wrap the job

from apscheduler.schedulers.blocking import BlockingScheduler
import runvouch

def nightly_report():
    with runvouch.vouch("nightly-report", evidence=lambda: {"rows": n > 0}) as run:
        n = build_report(run)

sched = BlockingScheduler()
sched.add_job(nightly_report, "cron", hour=2, minute=0, misfire_grace_time=3600)
sched.start()

rv fails open: if RunVouch is unreachable the job still runs and you get one warning line.

Register the cadence and caps

rv agent nightly-report --cadence 24h --grace 30m --max-runtime 1h --evidence --cap-run-cost 2

Register the agent once, from anywhere with the key. Cadence is what turns a schedule that stopped into an alert; --evidence makes a run without evidence a failure; the caps pause the agent when it overspends.

What goes silent on APScheduler (in-process)

• A job missed while the process was down is dropped after misfire_grace_time; with the default (1 second in APScheduler 3) it is dropped almost always.
• Two replicas of the process run the job twice; RunVouch shows both runs under one agent, and the daily cost cap counts both.
• A process stuck on a lock still looks alive to the orchestrator; STALLED catches the run that never ends.

What RunVouch detects

Need a key? Get a free key · Stuck? contact