Sign in
operator-runs

Resolve Post Install Warranty Exception

Mark one flagged case as handled (retry scheduled / resolved without retry).

Records the resolution on the job's existing pilot_workflow_requests ledger row (found by its deterministic request_id), so there is no separate table:

  • resolved_no_retry / already_registered -> finalized (status 'resolved'); the daily pipeline skips it and the case is hidden permanently.
  • schedule_retry / error_fixed -> reopened to status 'ready', so the next enqueue run dispatches the stored Pilot request for another attempt. The org-scoped request_id means one org can never resolve another org's case.
post/warranty-runs/post-install/exceptions/resolve

Request body

case_keystring required
resolution'schedule_retry' | 'resolved_no_retry' | 'error_fixed' | 'already_registered' required
job_idstring nullable
kindstring nullable
reasonstring nullable
notestring nullable

Response

Successful Response

{"stackTrail":"paths:/warranty-runs/post-install/exceptions/resolve:post:responses:200:content:application/json:schema","oasType":"schema","type":"unknown"}

Changes