---
title: "Reset workflow run"
method: POST
path: "/api/v1/workflow_runs/{workflowRunID}/reset"
tags: ["Workflow Run"]
---

# Reset workflow run

`POST /api/v1/workflow_runs/{workflowRunID}/reset`

Resetting the workflow run leads to:
- change its workflow status to `in_review`
- empty annotation's `assignees`
- set the annotation status to `to_review`
- create workflow activity of action `pushed_back`

<Callout type="info">
Resetting is allowed only for workflow runs with related annotation in `in_workflow` state. See [Annotation Lifecycle](/guides/annotation-lifecycle) for more information about states.
</Callout>

## Path parameters

- `workflowRunID` integer, required

## Request body

- ResetRequest
  - `note_content` string — String note for the reset action

## Response `200`

OK

- ResetResponse
  - `annotation_status` string — New status of the annotation (to_review)
  - `workflow_status` string — New workflow status (in_review)

## Other responses

- `400` — Invalid input data.
- `401` — The username/password is invalid or token is invalid (e.g. expired).
- `403` — Insufficient permission, missing authentication, invalid CSRF token and similar issue.
- `404` — The specified resource was not found.
- `409` — Conflict
- `413` — Payload too large (especially for files uploaded).
- `429` — Request rate is too high, wait before sending more requests. See [Rate Limiting](/guides/overview#rate-limiting) for more details.
- `500` — Server failure while processing the request.
- `502` — Invalid response from the upstream server.
- `503` — We're temporarily offline for maintenance. Please try again later.
- `504` — Upstream server could not complete the request in time.

---

[API](https://skmtc.dev/rossum/apis/rossum-api.md) · [All operations](https://skmtc.dev/rossum/apis/rossum-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/rossum/rossum-api/revisions/f1b5a910991d/schema)