---
title: "Continue Team Run"
method: POST
path: "/teams/{team_id}/runs/{run_id}/continue"
tags: ["Teams"]
---

# Continue Team Run

`POST /teams/{team_id}/runs/{run_id}/continue`

Continue a paused or incomplete team run with updated requirements.

**Use Cases:**
- Resume execution after tool approval/rejection
- Provide manual tool execution results
- Resume after admin approval (requirements can be empty; resolution fetched from DB)

**Requirements Parameter:**
JSON string containing array of requirement objects with tool execution results.
Can be empty when an admin-required approval has been resolved.

## Path parameters

- `team_id` string, required
- `run_id` string, required

## Response `200`

Team run continued successfully

- unknown

## Other responses

- `400` — Invalid JSON in requirements field or invalid requirement structure
- `401` — Unauthorized
- `403` — Run has a pending admin approval and cannot be continued by the user yet.
- `404` — Team not found
- `409` — Run is not paused (e.g. run is already running, continued, or errored). Only PAUSED runs can be continued.
- `422` — Validation Error
- `500` — Internal Server Error

---

[API](https://skmtc.net/agno/apis/agno-api-reference.md) · [All operations](https://skmtc.net/agno/apis/agno-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/agno/agno-api-reference/revisions/5f6149d395d0/schema)