pub struct GetHealthResponse {
pub status: Option<GetHealthResponseStatus>,
pub timestamp: Option<String>,
pub kv_connected: Option<bool>,
pub uptime_seconds: Option<f64>,
pub version: Option<String>,
pub build_sha: Option<String>,
pub pending_resumes: Option<i64>,
pub runs_queued: Option<i64>,
}Expand description
GetHealthResponse model.
Fields§
§status: Option<GetHealthResponseStatus>§timestamp: Option<String>§kv_connected: Option<bool>§uptime_seconds: Option<f64>§version: Option<String>The API contract version, a DATE STAMP — 2026-09-10 — bumped only on a breaking change,
and the same value the X-API-Version RESPONSE header carries. The server does not read a
request header of that name: pinning a date negotiates nothing. Not a release number and not
semver: it cannot be ordered against a semver string, so a client that compares it to one is
wrong in a way that appears to work for as long as both happen to sort the same. Compare it
for equality, or read it as a date. It says nothing about which BUILD is running — for that,
read build_sha.
build_sha: Option<String>The commit this running build was made from, baked in at image build time. This is the only
value on the wire that identifies the deployed code: version is the contract stamp and is
constant across deploys, and a restart proves a restart rather than an identity. "unknown"
means the image was built without the build argument (a local build, or a deploy predating
this field) and must be read as UNKNOWN, never as a match. Documentation that pins a claim
about platform behaviour can cite it.
pending_resumes: Option<i64>Always 0. Kept for compatibility — there is no resume-parking state: RunStatus has no
waiting_for_resume, and startup reconciliation FAILS an interrupted run rather than
holding it for resume. It previously reported the queue depth under this name, which reads
as recovery progress on the one endpoint an operator watches during a deploy. Use
runs_queued for the queue, and run status for recovery.
runs_queued: Option<i64>Runs currently queued. After a restart this includes runs reconciliation re-queued, so it falls as they are picked up — but it is a queue depth, not a count of recoveries.
Trait Implementations§
Source§impl Clone for GetHealthResponse
impl Clone for GetHealthResponse
Source§fn clone(&self) -> GetHealthResponse
fn clone(&self) -> GetHealthResponse
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more