From 4b5c8a1bf07d5a328756f50420c471082b4e6c4c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=E2=80=9CKevin=E2=80=9D?= <kevlar_ksb@yahoo.com>
Date: Thu, 6 Nov 2025 09:39:22 -0800
Subject: [PATCH] See Start Workflow in Action added to blog
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Signed-off-by: “Kevin” <kevlar_ksb@yahoo.com>
---
 .../2025-10-12-controlling-workflows-from-web.md               | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/blog/2025-10-12-controlling-workflows-from-web/2025-10-12-controlling-workflows-from-web.md b/blog/2025-10-12-controlling-workflows-from-web/2025-10-12-controlling-workflows-from-web.md
index 05817057d..71c66c870 100644
--- a/blog/2025-10-12-controlling-workflows-from-web/2025-10-12-controlling-workflows-from-web.md
+++ b/blog/2025-10-12-controlling-workflows-from-web/2025-10-12-controlling-workflows-from-web.md
@@ -6,6 +6,8 @@ tags:
   - release
   - announcement
 ---
+## See Start Workflow in Action
+<iframe width="560" height="315" src="https://www.youtube.com/embed/juQhG8JIMvc?si=5YYwIFjGuSgkKR1z" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
 
 For a long time, controlling Cadence workflows was primarily done through the client SDKs or the administrative CLI. Our vision for **Cadence Web** has been to evolve it from a read-only inspection tool into a **Unified Operational Hub** for all workflow management needs. This means putting every essential workflow action directly in the hands of operators, support engineers, and developers—right where they observe workflows.
 
@@ -15,6 +17,7 @@ Today, we’re completing that journey with the introduction of the **`Start Wor
 
 ***
 
+
 ## Where to Find the New Controls
 
 All workflow actions are designed to be discoverable and intuitive, fitting naturally into existing pages and workflows.