Retest the fix of an accepted Triage finding
Start a retest of the fix of one accepted finding of your team. A retest is a run of kind retest on the same finding: Neo checks whether the fix holds against the fix links of the review (pull request, repository and staging target, all treated as untrusted data) and reports retest_outcome fixed, not_fixed or blocked. The claim, the fix status retesting and a retest_requested event are one transaction. A retest never changes the inbox verdict or latest_run; the newest retest is latest_retest. When the retest ends, fixed sets the fix to fixed with an undoable retest_completed event, not_fixed returns it to PR linked and blocked leaves it unchanged; a failed retest restores the fix status it had before. Members and admins; requires Neo AI access and available credits.
Authorizations
JWT authentication token
Path Parameters
Finding id
Body
Optional model to use for triage. An invalid value rejects the request before a run is claimed.
Response
The retest run was claimed and its task queued
One triage run of a finding. Runs are append-only.
The finding revision this run triages.
triage for a run a member started, auto for an auto triage run, retest for a retest of the fix of an accepted finding.
triage, auto, retest Model requested for the run. Empty means the default.
queued, running, completed, failed, cancelled Stable failure code when status is failed, such as enqueue_failed.
The outcome of a retest run. Null for other runs.
fixed, not_fixed, blocked Neo task id of this run once dispatched.
Current Neo task status, when the run has a task.
pending, active, completed, error, aborted, suspended Neo suggested severity. Only set when triage_status is valid.
none, low, medium, high, critical, unknown Neo disposition. Null until the run records a decision.
valid, need_more_info, duplicate, informative, not_applicable, spam, unknown 
