KOkobaltlabs
internal

Abandon Sweep

Changed on

Stop a sweep and release the company, without waiting out Hatchet's timeouts.

The recovery path for a sweep whose worker was evicted: the row says RUNNING, nothing will move it, and reap_stale_sweeps does not touch it for nine hours — during which the company cannot be swept, because the row it would clear is the one blocking the start that would clear it.

post/internal/evals/rollout-consistency/sweeps/{sweep_id}/abandon

Request

  • Base URL
    https://api.kobaltlabs.com (the document declares no server; this is the origin it was published from)
  • URL
    https://api.kobaltlabs.com/internal/evals/rollout-consistency/sweeps/{sweep_id}/abandon
  • Auth
    none declared

Path parameters

sweep_idstring uuid required

Response

Successful Response

sweep_idstring uuid required
company_idstring uuid required
company_namestring nullable required
window_daysinteger required
status'queued' | 'running' | 'succeeded' | 'failed' required

Lifecycle of one sweep. Mirrors ApplicabilityRunStatus deliberately.

stage'queued' | 'gathering' | 'analysing' | 'comparing' | 'done' required

What the sweep is doing right now.

Committed before the work it names starts, so a watcher sees the stage currently taking the time rather than the last one that finished. ANALYSING is where nearly all of it goes.

stalledboolean required
rollout_enrolledboolean required
createdstring date-time required
finished_atstring date-time nullable required
collateral_analysedinteger required
visible_agreement_ratenumber nullable required
visible_flipsinteger required
agreement_ratenumber nullable required
flagged_lostinteger required
dismissed_reintroducedinteger required

Changes

  • 9fe2fb8a3631Revision changes
    • info

      added the required property to the response with the status

    • info

      added the required property to the response with the status