adding-instance-restarts-changelog-entry

src/content/changelog/workflows/2025-11-12-instance-restarts.mdx

@@ -0,0 +1,23 @@
+---
+title: Instance restarts now supported in Workflows
+description: You can now restart an instance of your Workflow without losing its concurrency spot
+products:
+  - workflows
+  - workers
+date: 2025-11-12
+---
+
+You can now restart a [Cloudflare Workflow](/workflows/) instance via the [API](/api/resources/workflows/methods/list/), [Wrangler](/workers/wrangler/commands/#workflows), or [Workers](/workflows/build/workers-api/):
+
+```typescript
+let instance = await env.MY_WORKFLOW.get("abc-123");
+await instance.restart(); // Returns Promise<void>
+```
+
+You may want to [restart an instance](/workflows/build/trigger-workflows/#restart-a-workflow) if the Workflow has been updated, the parameters have changed, or the Workflow has reached its step limit. This allows you to make changes without waiting until the instance is complete or preserve a long-running instance through restart. Restarting an instance will immediately cancel any in-progress steps, erase any intermediate state, and treat the Workflow as if it was run for the first time.
+
+If the instance is already running, the restart will not lose its concurrency slot (limit of 10,000 concurrent instances). For example, say you have 10,000 instances running and 2,000 instances queued. If you restart a runnning instance, it will maintain its spot in the 10,000 rather than slotting into the back of the queue.
+
+However, note that the restarted instance will count towards the instance creation rate limit (100 Workflow instances per second). 
+
+For more information on concurrency and creation limits, refer to [Workflow limits](/workflows/reference/limits/).