Reflect resilient deployments on Octopus Cloud

Deployments and runbook runs on Octopus Cloud now survive node restarts
and maintenance windows: they pause and resume automatically rather than
failing. Update the customer-facing docs that still framed task failure
during outages as expected behaviour.

- maintenance-window: replace the "resilience is future roadmap work"
  hint with shipped behaviour; scope the shutdown-timeout note to
  deployments/runbook runs (other system tasks may still be abandoned)
- Cloud FAQ: add "What happens to my deployments during a maintenance window?"
- bulk-operations rerun script: add a Cloud-obsolescence note (still
  relevant for self-hosted HA)

Scope is Octopus Cloud only. Self-hosted HA pages are intentionally left
unchanged — resilience is not yet on self-hosted.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: lucyjspence

src/pages/docs/octopus-cloud/frequently-asked-questions.md

@@ -1,7 +1,7 @@
 ---
 layout: src/layouts/Default.astro
 pubDate: 2024-11-08
-modDate: 2024-11-08
+modDate: 2026-06-22
 title: Octopus Cloud Frequently Asked Questions
 navTitle: Octopus Cloud FAQ
 navOrder: 70
@@ -200,6 +200,10 @@ We publish Octopus Cloud’s [uptime track record](/docs/octopus-cloud/uptime-sl
 
 We publish Octopus Cloud's [operational status](https://status.octopus.com/). You can subscribe to status change emails from our [operational status page](https://status.octopus.com/).
 
+### What happens to my deployments during a maintenance window?
+
+Deployments and runbook runs on Octopus Cloud are resilient. If a [maintenance window](/docs/octopus-cloud/maintenance-window) or node restart interrupts a deployment or runbook run, it is paused and resumes automatically once your instance is back online, rather than failing. You don't need to drain tasks or manually re-run them afterwards.
+
 ## Logs and data
 
 ### How do we access deployment and audit logs? 

src/pages/docs/octopus-cloud/maintenance-window.md

@@ -1,7 +1,7 @@
 ---
 layout: src/layouts/Default.astro
 pubDate: 2023-01-01
-modDate: 2024-11-27
+modDate: 2026-06-22
 title: Octopus Cloud Maintenance Window
 navOrder: 55
 description: Details about the Octopus Cloud maintenance window
@@ -53,13 +53,13 @@ Many of those tasks have guard clauses. For example, we won't de-fragment a data
 It is important to note that most maintenance tasks do not start at the beginning of your maintenance window. We host thousands of customer instances. Because of that, we perform maintenance tasks in bulk. When we run a maintenance task, your instance might be the first, somewhere in the middle, or at the end of the list of instances. In some cases, by the time we finish processing other instances, your maintenance window is about to end. When that happens, your instance is skipped and that task won't be processed until the next day. That typically happens when performing upgrades. 
 
 :::div{.hint}
-Upgrading an instance is the primary cause of outages. The most noticeable impact of an outage is deployments and runbook runs may fail. We are actively working on [Resilient Scalable Deployments](https://roadmap.octopus.com/c/95-alpha-program-resilient-scalable-deployments-in-octopus-cloud) to allow deployments and runbook runs to continue post-upgrade.  
+Upgrading an instance is the primary cause of outages. Deployments and runbook runs on Octopus Cloud are now resilient: if an outage interrupts a deployment or runbook run, it is paused and resumes automatically once your instance is back online, rather than failing. You no longer need to drain tasks or manually re-run deployments and runbook runs after a maintenance window.
 :::
 
 ## Taking your instance offline
 
 If we need to take your instance offline to perform any maintenance:
-- Your instance will be given a few minutes to shut down cleanly. This will allow any in-progress tasks to complete. Any tasks still running at the end of the timeout will be abandoned.
+- Your instance will be given a few minutes to shut down cleanly. This will allow any in-progress tasks to complete. Deployments and runbook runs still in progress at the end of the timeout are resilient — they are paused and resume automatically once your instance is back online, rather than failing.
 - A maintenance page will be displayed to users and any requests to the API will return a 503 Service Unavailable status code.
 - The maintenance operations will be performed.
 - Your instance will start up again and we will check that it is in a healthy state.

src/pages/docs/octopus-rest-api/examples/bulk-operations/rerun-deployments-and-runbooks-after-node-shutdown.mdx

@@ -1,12 +1,16 @@
 ---
 layout: src/layouts/Default.astro
 pubDate: 2023-01-01
-modDate: 2023-01-01
+modDate: 2026-06-22
 title: Rerun all canceled deployments and runbook runs after node shutdown.
 description: An example script that determine which deployments and runbook runs were canceled because of a node shutdown and resubmit them.
 ---
 import RerunDeploymentsAndRunbooksAfterNodeFailure from 'src/shared-content/scripts/rerun-deployments-and-runbooks-after-node-failure.include.md';
 
+:::div{.hint}
+**Octopus Cloud:** This script is no longer needed for deployments and runbook runs. On Octopus Cloud, these tasks are resilient — they are paused and resume automatically after a node restart or maintenance window rather than being cancelled. This script remains useful for self-hosted High Availability instances, where node restarts still cancel active tasks.
+:::
+
 This script demonstrates how to programmatically determine which deployments and runbook runs can be resubmitted because they were canceled because of a node shutdown.  The node could have been shutdown for normal reasons, or it could have stopped responding, or it could have been turned off.
 
 ## Usage