OntologyResyncRun
Active/last-known resync worker run summary. active still means "a run is in flight"; the other fields describe the last run whatever its state, so a failed one stops being invisible. The worker records its cause in the marker's description (workflows/resync.py), and reporting only in-flight runs threw that away — a resync could fail repeatedly while this endpoint said nothing.
True when a resync worker run is in flight
run_id object
Run id of the last run
- string
- null
state object
Run state of the last run (running / completed / failed)
- string
- null
description object
Failure cause of the last run; null when it succeeded, is still in flight, or the caller is not admin/manager (the text is an exception verbatim, so it is redacted for everyone who cannot act on it)
- string
- null
start_time object
Unix ms the last run started
- integer
- null
end_time object
Unix ms the last run finished; null while running
- integer
- null
{
"active": true,
"run_id": "string",
"state": "string",
"description": "string",
"start_time": 0,
"end_time": 0
}