---
title: "Resume an invocation"
method: PATCH
path: "/invocations/{invocation_id}/resume"
tags: ["invocation"]
---

# Resume an invocation

`PATCH /invocations/{invocation_id}/resume`

Resumes a paused or suspended invocation. If the invocation is backing off due to a retry, this will immediately trigger the retry.
Optionally, you can change the deployment ID that will be used when the invocation resumes. For more information see [resume documentation](https://docs.restate.dev/services/invocation/managing-invocations#resume)

## Path parameters

- `invocation_id` string, required

## Query parameters

- `deployment` union
  - 'Keep' — Keep the currently pinned deployment
  - 'Latest' — Use the latest deployment
  - object — Use a specific deployment ID
    - `Id` string, required — Use a specific deployment ID

## Response `200`

Invocation resumed successfully

## Other responses

- `400` — The selected deployment id to resume the invocation doesn't support the currently pinned service protocol version.
- `404`
- `409` — The invocation is still running or the deployment id is not pinned yet, deployment id cannot be changed. The deployment id can be changed only if the invocation is paused or suspended, and a deployment id is already pinned.
- `425` — The invocation is either inboxed or scheduled. An invocation can be resumed only when running, paused or suspended.
- `503` — Error when routing the request within restate.

## Changes

- **2026-01-30** `059a44500a5c` — 1 info
  - for the `query` request parameter `deployment`, the type/format was generalized from `string`/`` to ``/``

[Change history](https://skmtc.dev/restatedev/apis/admin-api/changes/invocations/:invocation_id/resume/patch.md)

---

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