---
title: "Update Subtask Status"
method: PUT
path: "/api/datasubject/v2/subtasks/{subtaskId}/status"
tags: ["Subtasks"]
---

# Update Subtask Status

`PUT /api/datasubject/v2/subtasks/{subtaskId}/status`

Use this API to update the status of an existing subtask.

> 🗒 Things to Know
>
> - The following statuses can be passed as parameter values in the request: `IN_PROGRESS`, `FAILED`, `COMPLETED`, and `REJECTED`.
> - The Resolution ID can only be passed if the subtask status is updated to `COMPLETED` or `REJECTED`.

## Path parameters

- `subtaskId` string, uuid, required — Subtask Id

## Request body

- PrivacyAutomationDataSubjectRequestDSRAutomationUpdateSubtaskStatusRequest
  - `comment` string — Comments can be updated for system subtask status call - this can be used for reason for failure. Longer comments may impact system performance.
  - `status` 'IN_PROGRESS' | 'FAILED' | 'COMPLETED' | 'REJECTED', required — Status to be updated to completed or failed
  - `resolutionId` string, uuid — Resolution ID (can only be passed if the subtask status is updated to COMPLETED or REJECTED)

## Response `200`

OK

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Forbidden
- `429` — Too Many Requests. For more information, see [API Rate Limits](https://developer.onetrust.com/onetrust/reference/rate-limits-overview).
- `500` — Internal Server Error

---

[API](https://skmtc.net/onetrust/apis/platform-access-management.md) · [All operations](https://skmtc.net/onetrust/apis/platform-access-management/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/onetrust/platform-access-management/versions/21de3aa0b170/schema)