# A hand-kept list of scheduled jobs drifts from what's actually running

Generate the job registry daily, and keep intent apart from wiring.

By Ki Moon · 2026-10-06 · technique · current
Canonical: https://kihmoon.com/bench-notes/p/automation-inventory-drifts/

**Symptom:** Two docs disagree on whether a scheduled job is live, and its config passes no live or dry flag.

Dozens of recurring jobs run my GTM automation across five surfaces. They are the laptop scheduler, desktop tasks, cloud routines, managed agents and one interactive session. The registry was prose I had to remember to edit.

An audit found about one loaded job in five with no row, and nearly as many rows with the wrong schedule.

A script with no model now generates the registry every day from what is loaded, its schedule, its last fire and its result. A new job appears the day it is loaded.

A second audit showed a config can't say whether a job is live. Only about one in five job configs passed an explicit live flag. The rest passed nothing, and nothing meant live for some and dry for others.

So I record intent, what I want, apart from mode, what is wired today. A daily check reports the gap between them under its own "built, not live" verdict.

A scheduler read from a periodic cache rather than live lags by up to the cache's age, so the check also flags any cache older than its refresh interval.

## Check your setup (read-only)

Compare your written job registry with the scheduler's loaded-job list and each job's config file. Match on the job's label. Read each schedule from the config file itself, not from a comment beside it. Look in the job's own code for a guard that skips the extra runs before you count a schedule difference. Any loaded job missing from the registry is a gap. Any schedule that differs between the registry and the config file is a gap. Any config that can't say live or dry is a gap.

**Passes if:** Every loaded job appears in the registry with the same schedule, and every job config states live or dry.

**Access needed:** scheduler, local-config

## If it fails (changes to make later, not part of the check)

1. Generate the job registry daily from every scheduler's loaded state, with no model in the path.
2. Hand-keep only fields no script can derive, such as which system a job belongs to and what it feeds.
3. Record each job's intent apart from its wired mode. Intent is live, paused or retired. Mode is live, dry or partial. Record the date the mode began.
4. Flag every job with intent live and mode dry or partial as "built, not live", with its age.
5. Open a go-live ticket for any job that has sat in that state for 14 days without one. Put the exact commands in the ticket.

**Applies if:** Your setup has a written job registry and loads jobs in 2 or more schedulers.

**Skip if:** All your jobs live in one scheduler whose own console shows each job's live state.

Tags: drift, observability, reliability
