Docs › Temporal Schedule monitoring with RunVouch
Temporal Schedule monitoring with RunVouch
Temporal Schedule monitoring for eventually: a Temporal Schedule starts workflows on time; a worker polling the task queue executes them. With no worker, workflow tasks wait in the queue indefinitely with no error, because from Temporal's point of view nothing is wrong yet.
How it runs on Temporal Schedules
Inside the workflow's first and last activity, or around the worker process if one workflow per process. Use the two HTTP calls from an activity (activities may do I/O; workflows must not).
Store the key
An environment variable on the worker.
Wrap the job
# activities.py (activities may do I/O; workflows must not)
import os, requests
from temporalio import activity
H = {"X-API-Key": os.environ["RUNVOUCH_KEY"], "content-type": "application/json"}
@activity.defn
async def start_run(agent: str) -> str:
return requests.post("https://api.runvouch.com/v1/runs/start", headers=H, timeout=10,
json={"agent": agent, "source": "temporal"}).json()["run_id"]
@activity.defn
async def end_run(run_id: str, ok: bool, rows: int) -> None:
requests.post("https://api.runvouch.com/v1/runs/end", headers=H, timeout=10,
json={"run_id": run_id, "status": "ok" if ok else "fail", "evidence": {"rows": rows > 0}})
# the schedule, once: temporal schedule create --schedule-id nightly-report --cron "0 2 * * *" \
# --workflow-type NightlyReport --task-queue reportsrv 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 Temporal Schedules
- No worker on the task queue means the schedule fires and the work waits; the schedule's own counters say "running". MISSED and STALLED both apply.
- Activity retries are unlimited by default; an LLM activity that keeps failing keeps spending. The per-run cap ends it.
- Overlap policy Skip drops a start; that is a MISSED you would otherwise not see.
What Temporal Schedules does not tell you
Temporal's Schedule keeps counters of actions taken and skipped and the Web UI shows workflow status; there is no built-in notification for a workflow that has been Running for hours because no worker is polling, or for a Schedule whose overlap policy skipped a start. Workflow timeouts (execution_timeout) turn a stuck workflow into a failure only if you set them.
What RunVouch detects
| Alert | What it means here |
|---|---|
| MISSED | cadence plus grace passed and no run started |
| FAILED | non-zero exit or a reported failure, with the stderr excerpt |
| NO_EVIDENCE | the run said ok but the file, URL or assertion you required is missing |
| STALLED | a run started and never ended within max runtime |
| RETRY_STORM | the same tool called with identical input many times in one run |
| BUDGET_RUN / BUDGET_DAY | cost cap crossed; the agent is paused until you resume it |
| DRIFT | duration or output size far off its 7-run baseline |
Set up in two minutes
- Get a free key (3 agents, no card) and store it where this page says.
- wrap the job: copy the snippet above into the scheduled job.
- Register the cadence once:
rv agent nightly-report --cadence 24h --grace 30m --evidence, or let the first run create the agent and set the cadence on the dashboard. - Send one test alert:
curl -X POST https://api.runvouch.com/v1/settings/test-alert -H "X-API-Key: $RUNVOUCH_KEY". The next missed, failed or empty run reaches the same channels.
Also running orchestrators?
Windmill. node-cron. PM2 cron restart. BullMQ job schedulers. The full list of runtimes is on integrations, and the same agent can report from several of them: one job, one cadence, wherever it happens to run.
Need a key? Get a free key · Stuck? contact