eugenegujing opened a new issue, #6846: URL: https://github.com/apache/texera/issues/6846
### What happened? Using the **Import Workflow** button in the workspace toolbar (`frontend/src/app/workspace/component/menu/menu.component.ts` → `onClickImportWorkflow`) to import a workflow JSON into the currently open workflow **A** leaves a brand-new workflow **B** in the user's workflow list, with content identical to the imported file. Replacing the content of the current workflow A with the imported content is the intended behavior of this button. The bug is only the extra workflow B: a single import silently creates an additional, unwanted workflow that the user never asked for. **Expected:** importing replaces the content of the current workflow A in place (A keeps its own `wid`), and **no** additional workflow is created in the list. ### How to reproduce? 1. Log in and open an existing workflow **A**, so A has a real `wid`. 2. In the workspace toolbar, click **Import Workflow** and select a workflow JSON 3. Observe the canvas now shows the imported content. 4. Wait for auto-persist (~debounce), then open the workflows list. Observed: a new workflow B identical to the import appears in the list (in addition to A), and the URL has switched to B's wid. Expected: A's content is replaced in place, A keeps its wid, and no new workflow B is created. ### Version/Branch 1.3.0-incubating-SNAPSHOT (main) ### Commit Hash (Optional) _No response_ ### What browsers are you seeing the problem on? _No response_ ### Relevant log output ```shell ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
