stado coordinator
Invocation
stado coordinator [OPTIONS]Purpose
Run the provider-neutral scheduling tick locally. Reads cadence and identity from the named coordinator entry. Queue, registry, capacity, and schedule state use the configured Stado storage backend.
Required inputs and options
| Input or option | Contract |
|---|---|
--target <TARGET> | Coordinator name or host heuristic (default: active=true entry) |
--once | Run a single scheduling tick and exit (cron-friendly) |
Output and state effect
It performs the operation described above and emits its operator result on standard output or standard error. Any state change is limited to the resources and records named by the purpose and options on this page.
Refusals
- Before dispatch, Stado refuses a missing required token shown in the invocation, an unknown option, or a value outside a listed value set; argument-usage failures exit with code 2.