Reopen a failed assessment
POST/api/v1/assessments/:assessment_id/reopen
Put a failed assessment back into a state the customer can act on.
One verb for both failures, because the customer's question is the same: this did not work, let me try again. The server picks the furthest-forward state it can safely restore, and the response says where it landed.
start_failedreturns toready. The spawn never ran, so the validation and merged archive are still good and no re-scan is needed. Capped atMAX_START_RETRIESattempts.failedreturns todraft, which is editable, startable and deletable. A failed run could not be removed at all before, only archived.
Credits were refunded when the run failed; /start charges again.
409 when the status is neither, when a failed run's cause was the customer's
own cancellation, when the retry cap is spent, or when the run left findings
or a report behind, since reopening would then put a delete button in front
of delivered work.
- Scope required:
assessments:update+ manager-or-above role.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 422
- 429
- 500
Successful Response
Bad request — malformed input or failed validation.
Missing, expired, or invalid credentials.
Authenticated but not authorized for this resource. Note: cross-organization reads return 404, not 403.
Resource not found, or hidden for tenant-enumeration safety (the caller lacks permission to know whether the resource exists).
Conflict — the current resource state does not allow this operation (e.g. assessment already started, email already in use).
Semantic validation failure — request shape was valid but contents were not.
Too many requests — rate limited. Retry after the window resets.
Internal server error — unexpected failure.