From e1affd91c20246ace851915cb23e7c2ff7519fd7 Mon Sep 17 00:00:00 2001
From: abhizipstack <abhishek@zipstack.com>
Date: Wed, 8 Apr 2026 12:36:02 +0530
Subject: [PATCH] fix: remove loader reset from finally block in set-model
 handler

The .finally() block was resetting setIsLoading(false) after both
success and error paths. On success, this interfered with the loading
state needed by runTransformation. The catch block already handles
the error path loader reset.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---
 frontend/src/ide/editor/no-code-model/no-code-model.jsx | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/frontend/src/ide/editor/no-code-model/no-code-model.jsx b/frontend/src/ide/editor/no-code-model/no-code-model.jsx
index 8f3fa3f..80304d0 100644
--- a/frontend/src/ide/editor/no-code-model/no-code-model.jsx
+++ b/frontend/src/ide/editor/no-code-model/no-code-model.jsx
@@ -746,9 +746,6 @@ function NoCodeModel({ nodeData }) {
         notify({ error });
         setIsLoading(false);
         handleModalClose();
-      })
-      .finally(() => {
-        setIsLoading(false);
       });
   };