From 15b0215da84f9b6a8b8dfb56f2881ceb1bea3b53 Mon Sep 17 00:00:00 2001
From: Matt <6519811+mattgogerly@users.noreply.github.com>
Date: Tue, 20 Jun 2023 11:19:08 +0100
Subject: [PATCH] chore(docs): Update zombie execution info

@dbyron-sf
---
 content/en/docs/guides/runbooks/orca-zombie-executions.md | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/content/en/docs/guides/runbooks/orca-zombie-executions.md b/content/en/docs/guides/runbooks/orca-zombie-executions.md
index fb59943e..9f4cd15d 100644
--- a/content/en/docs/guides/runbooks/orca-zombie-executions.md
+++ b/content/en/docs/guides/runbooks/orca-zombie-executions.md
@@ -104,7 +104,13 @@ If any part of an Execution cannot be re-hydrated, the entire Execution will be
 ## Cancel the Execution
 
 If the Execution cannot be rehydrated, it will need to be canceled.
-You can cancel the Execution via the UI or force cancellation via an Orca admin API:
+
+> Note: Prior to Spinnaker 1.32.0, cancelling a zombied execution via the UI
+> did not work. If you still encounter issues cancelling executions via the UI please
+> open a [GitHub issue](https://github.com/spinnaker/spinnaker/issues/new).
+
+If cancelling an executuon from Deck does not work, you can force cancellation 
+via an Orca admin API:
 
 ```
 PUT /admin/forceCancelExecution?executionId=01CS076X85RX6MWBTQ0VGBF8VX&executionType=PIPELINE