---
title: "Restart invocation as new"
method: PATCH
path: "/invocations/{invocation_id}/restart-as-new"
tags: ["invocation"]
---

# Restart invocation as new

`PATCH /invocations/{invocation_id}/restart-as-new`

Creates a new invocation from a completed invocation, optionally copying partial progress from the original invocation's journal.
The new invocation will have a different invocation ID. Use the `from` parameter to specify how much of the original journal to preserve.

## Path parameters

- `invocation_id` string, required

## Query parameters

- `from` integer
- `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 restarted successfully with a new invocation ID

- RestartAsNewInvocationResponse — The invocation was restarted as new.
  - `new_invocation_id` string, required

## Other responses

- `400` — The selected deployment id to restart as new 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.
- `410` — The invocation cannot be restarted because the input is not available. In order to restart an invocation, the journal must be available in order to read the input again. Journal can be retained after completion by enabling journal retention.
- `422` — Restarting the invocation is not supported. Restarting workflows is not supported, and restarting invocations created using the old service protocol.
- `425` — The invocation cannot be restarted because it's not running yet, meaning it might have been scheduled or inboxed.
- `503` — Error when routing the request within restate.

## Changes

- **2026-01-30** `059a44500a5c` — 1 breaking, 3 info
  - the `new_invocation_id` response's property type/format changed from ``/`` to `string`/`` for status `200`
  - for the `query` request parameter `deployment`, the type/format was generalized from `string`/`` to ``/``
  - for the `query` request parameter `from`, the type/format was generalized from `integer`/`uint32` to ``/``
  - removed `#/components/schemas/String` from the `new_invocation_id` response property `allOf` list for the response status `200`

[Change history](https://skmtc.dev/restatedev/apis/admin-api/changes/invocations/:invocation_id/restart-as-new/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)