From 34db4dcd5a756e4c8a96655ed293b0c4f8f8f3f5 Mon Sep 17 00:00:00 2001
From: Nicolas <nborges.aws@gmail.com>
Date: Tue, 28 Jan 2025 11:33:08 -0500
Subject: [PATCH] fix to display logic when failure condition overlaps with lsp
 failure

---
 .../toolkits/eclipse/amazonq/views/AmazonQChatWebview.java  | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/plugin/src/software/aws/toolkits/eclipse/amazonq/views/AmazonQChatWebview.java b/plugin/src/software/aws/toolkits/eclipse/amazonq/views/AmazonQChatWebview.java
index 3e2b6642..15fda4e2 100644
--- a/plugin/src/software/aws/toolkits/eclipse/amazonq/views/AmazonQChatWebview.java
+++ b/plugin/src/software/aws/toolkits/eclipse/amazonq/views/AmazonQChatWebview.java
@@ -142,9 +142,11 @@ public final void onEvent(final AuthState authState) {
                 // chat view
                 if (browser != null && !browser.isDisposed() && !chatStateManager.hasPreservedState()) {
                     Optional<String> content = getContent();
-                    if (!content.isPresent() && !LspStatusManager.getInstance().lspFailed()) {
+                    if (!content.isPresent()) {
                         canDisposeState = true;
-                        ViewVisibilityManager.showChatAssetMissingView("update");
+                        if (!LspStatusManager.getInstance().lspFailed()) {
+                            ViewVisibilityManager.showChatAssetMissingView("update");
+                        }
                     } else {
                         browser.setText(content.get()); // Display the chat client
                     }