Admin

Rollback pipeline plan

Restore an earlier immutable Pipeline Plan through a background Operation. plan_id defaults to the plan the active one replaced. Returning registrations must answer discovery with their exact manifest digest. Coverage gaps do not prevent rollback; affected records retain their outgoing owner and space until background recovery completes the returning projection. pinned_work chooses drain or stop for outgoing work; pinned Subscription Versions keep their evaluators. Follow Location; admin.plan_id names the new rollback plan. Requires plugins:admin.

post/v0/admin/plugins/plan/rollback

Request

  • Base URL
    https://docs.quivr.thevibecompany.co (the document declares no server; this is the origin it was published from)
  • Auth
    HTTP bearer

Request body

idempotency_keystring required
plan_idstring

The plan whose roles become active again; absent returns to the plan the active one replaced (its previous_plan_id).

pinned_work'drain' | 'stop'

What happens to work pinned to a plan naming a plugin version the rollback takes out. drain lets it finish on that version, which stays draining meanwhile. stop keeps it from calling that version again once each process follows the new plan (within plugin_plan_poll). Its next call fails instead. The processing of a Version then stops with the diagnostic pinned_plan_stopped, with the outcome of pinned_plugin_unavailable, and a rebuild fails with that code. A connector run fails as when its plugin is unavailable, and its next run uses the active plan.

Response

Accepted background Operation.

operation_idstring required
kindstring required
state'queued' | 'running' | 'paused' | 'succeeded' | 'failed' | 'cancel_requested' | 'canceled' required
progressnumber

Approximate fraction, omitted when unknown.

countersobject required
previous_operation_idstring
corpus_idstring

Changes

No recorded changes to this operation across all 1 revision of this API.