diff --git a/src/pages/docs/releases/manually-fail-a-task.md b/src/pages/docs/releases/manually-fail-a-task.md
index 1b3fba7ea2..dab8518da3 100644
--- a/src/pages/docs/releases/manually-fail-a-task.md
+++ b/src/pages/docs/releases/manually-fail-a-task.md
@@ -1,7 +1,7 @@
 ---
 layout: src/layouts/Default.astro
 pubDate: 2023-01-01
-modDate: 2024-08-29
+modDate: 2026-09-14
 title: Manually fail a task
 description: How to manually fail a running or canceling task when tasks hang or get stuck.
 icon: fa-solid fa-circle-stop
@@ -17,3 +17,7 @@ When a task is queued, you'll see a list of tasks that it is waiting on in the t
 :::
 
 You can navigate to any of these tasks, and then click the Cancel button in the top right corner on the executing/waiting/queued task (you may need to click it twice). This will mark the blocked task as Failed and then allow your new task to proceed.
+
+## Abandon a stuck task
+
+If a deployment or runbook run never finishes canceling, you can abandon it. Once a task has been canceling for more than 10 minutes, an **Abandon** button appears on the task page. Abandoning records the task as **Canceled** so it stops blocking work waiting on it, but it only changes what Octopus records: any scripts or steps already running on your deployment targets keep running untracked, the usual cancellation clean-up is skipped, and the action can't be undone. Treat it as a last resort when the stuck task is causing more harm than the inconsistency it leaves behind. You'll need the `TaskCancel` permission for the task's project and environment.