Api Health Running Job

Is a declared long-running shell job alive on this instance?

LIVENESS, added 2026-09-22. /persistent survives the container that wrote the declaration, so a pid alone proves nothing: after the deploy that killed the v49 fleet reparse, this endpoint still served running: true for pid 4115 on a pod where that pid does not exist, and the pre-push hook refused the RECOVERY push until an operator removed the file by hand. services/running_job.py compares the declaration's recorded writer (release, host, pid start) against THIS instance; a provably dead writer reads dead=True / running=False / stale=True, so even a pre-2026-09-22 hook that only knows running and stale degrades to its warn path. An UNPROVABLE liveness is never treated as dead — it falls back to the TTL, and says which it did in liveness.

get/api/health/running-job

Request

  • Base URL: https://www.oxfordledge.com (the document declares no server; this is the origin it was published from)
  • URL: https://www.oxfordledge.com/api/health/running-job
  • Auth: none declared

Response

Successful Response

runningboolean required

A declared job exists, is within its TTL, and is not provably dead. The pre-push hook refuses on True.

staleboolean required

A sentinel exists but exceeded its TTL (crashed job / missing cleanup), was unparseable, or is provably dead. Hook warns, never refuses.

namestring nullable

Operator-chosen job name from the sentinel, when present.

age_minutesnumber nullable

Minutes since the job declared itself.

ttl_hoursnumber nullable

The TTL the job declared at launch.

deadboolean

The declaring process is PROVABLY gone (a deploy replaced the instance, or the pid exited) — the sentinel is not protecting a job, regardless of its TTL.

livenessstring nullable

absent | alive | dead | unknown. 'unknown' means liveness could not be proven either way (a pre-v2 declaration, or a platform that cannot probe pids) and the TTL decided.

liveness_detailstring nullable

Why the liveness verdict came out that way, in categorical terms safe for a public body (no pids, paths or shas).

Changes

No recorded changes to this operation across all 1 revision of this API.