fixing issues

cortex-lp · cortex-lp · commit 1902f28cb6c6 · 2026-04-20T14:45:32.000+01:00
diff --git a/content/en/docs/2026.3/Guides/upgrade-guides/upgrade-cortex/2025.9-to-2025.9.26161/multiple-server-with-ha/_index.md.bak b/content/en/docs/2026.3/Guides/upgrade-guides/upgrade-cortex/2025.9-to-2025.9.26161/multiple-server-with-ha/_index.md.bak
diff --git a/content/en/docs/2026.3/Guides/upgrade-guides/upgrade-cortex/2025.9.26161-to-2026.3/multiple-server-with-ha/post-upgrade/move-flows-to-new-execution-service.md b/content/en/docs/2026.3/Guides/upgrade-guides/upgrade-cortex/2025.9.26161-to-2026.3/multiple-server-with-ha/post-upgrade/move-flows-to-new-execution-service.md
@@ -13,14 +13,6 @@ This guide describes how to move flow execution to the new Execution Service. Pl
 These steps are optional however it is recommended so that the new Execution Service is used after upgrade.
 {{% /alert %}}
 
-## Upgrade Flows
-
-{{< section "/upgrade/2026.3/upgrade-web-application-server/upgrade-flows.md" >}}
-
-{{% alert title="Note" %}}
-Once the flows have been upgraded it is necessary to {{< ahref path="Cortex.Guides.UpgradeGuides.UpgradeCortex.2025_9_26161to2026_3.MultipleServerWithHA.RepublishPackages" title="republish all packages" >}} that have previously been published.
-{{% /alert %}}
-
 ## Republish Packages
 
 {{< section "/upgrade/2026.3/upgrade-web-application-server/republish-packages.md" >}}
diff --git a/content/en/docs/2026.3/Guides/upgrade-guides/upgrade-cortex/2025.9.26161-to-2026.3/single-server-without-ha/post-upgrade/move-flows-to-new-execution-service.md b/content/en/docs/2026.3/Guides/upgrade-guides/upgrade-cortex/2025.9.26161-to-2026.3/single-server-without-ha/post-upgrade/move-flows-to-new-execution-service.md
@@ -9,12 +9,8 @@ weight: 20
 
 This guide describes how to move flow execution to the new Execution Service. Please ensure that the [Try it out][] steps have been completed before proceeding.
 
-## Upgrade Flows
-
-{{< section "/upgrade/2026.3/upgrade-web-application-server/upgrade-flows.md" >}}
-
 {{% alert title="Note" %}}
-Once the flows have been upgraded it is necessary to {{< ahref path="Cortex.Guides.UpgradeGuides.UpgradeCortex.2025_9_26161to2026_3.SingleServerWithoutHA.RepublishPackages" title="republish all packages" >}} that have previously been published.
+These steps are optional however it is recommended so that the new Execution Service is used after upgrade.
 {{% /alert %}}
 
 ## Republish Packages
diff --git a/data/urls.toml b/data/urls.toml
@@ -686,6 +686,7 @@
                     [Cortex.Guides.UpgradeGuides.UpgradeCortex.2025_3_26111to2026_3.MultipleServerWithHA]
                         PostUpgrade = "/docs/guides/upgrade-guides/upgrade-cortex/2025.3.26111-to-2026.3/multiple-server-with-ha/post-upgrade"
                         PreUpgrade = "/docs/guides/upgrade-guides/upgrade-cortex/2025.3.26111-to-2026.3/multiple-server-with-ha/pre-upgrade"
+                        RepublishPackages = "/docs/guides/upgrade-guides/upgrade-cortex/2025.3.26111-to-2026.3/multiple-server-with-ha/post-upgrade/move-flows-to-new-execution-service#republish-packages"
                         TryItOut = "/docs/guides/upgrade-guides/upgrade-cortex/2025.3.26111-to-2026.3/multiple-server-with-ha/post-upgrade/try-it-out/"
                         Upgrade = "/docs/guides/upgrade-guides/upgrade-cortex/2025.3.26111-to-2026.3/multiple-server-with-ha/upgrade"
                         UpgradeApplicationAndLoadBalancerServers = "/docs/guides/upgrade-guides/upgrade-cortex/2025.3.26111-to-2026.3/multiple-server-with-ha/upgrade/upgrade-application-and-loadbalancer-servers"
