Skip to main content

​
Usage

Request a stop for a Run. The result depends on its status, execution deadline, and whether dispatch has started:
  • If a synchronous Run has passed its execution deadline, timeout takes precedence: it settles as FAILED with failure kind TIMED_OUT, even if no Provider call has been recorded.
  • Otherwise, if no Provider call has been recorded, the Run becomes STOPPED, its Hold is closed, and its Charge is 0.
  • If a Provider call has already been recorded, the request records stop_requested_at. The Run continues to COMPLETED or FAILED. Its final Charge depends on the Endpoint’s pricing rules; read charge_usd from the Run.
  • A Run already in a terminal status returns HTTP 409, and the CLI exits 1.
Exit 0 means the stop request was accepted. The returned Run can still be RUNNING; check its status. Use glasser runs get -r <runId> --wait to retrieve its final status and Charge.

​
Flags

See CLI conventions for global flags, JSON mode, exit codes, and environment variables.