From 4dcbfb00ea720bab18fc6b0378c6c580c7863fb3 Mon Sep 17 00:00:00 2001
From: clay-codes <89403467+clay-codes@users.noreply.github.com>
Date: Tue, 15 Jul 2025 15:38:31 -0700
Subject: [PATCH] Update 1_19-failures-after-external-group-changes-standby.mdx
 (#31262)

Removing '...upgrade to 1.19.3' per cx request as issue still present on 1.19.3

Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
---
 .../1_19-failures-after-external-group-changes-standby.mdx       | 1 -
 1 file changed, 1 deletion(-)

diff --git a/website/content/partials/known-issues/1_19-failures-after-external-group-changes-standby.mdx b/website/content/partials/known-issues/1_19-failures-after-external-group-changes-standby.mdx
index bac4d98690..d176dea756 100644
--- a/website/content/partials/known-issues/1_19-failures-after-external-group-changes-standby.mdx
+++ b/website/content/partials/known-issues/1_19-failures-after-external-group-changes-standby.mdx
@@ -20,4 +20,3 @@ A related debug message may also appear in Vault server logs:
 
 #### Workaround
 Direct all logins and token renewals to the active node.
-Or upgrade to Vault 1.19.3+