Python Debugger Fails to Work Immediately After Creating a New Workflow

### What happened?

The Python Debugger does not function right after constructing a new workflow. When attempting to add a breakpoint in the Python UDF operator immediately after creating the workflow, the debugger is unresponsive. However, refreshing the page resolves the issue, and the debugger then works as expected.

### How to reproduce?

1. Create a new workflow containing a Python UDF operator (add a time.sleep() statement for testing).
2. Run the workflow.
3. Open the Python UDF operator and attempt to add a breakpoint. The UI doesn't allow me to do so.
4. Kill the workflow.
5. Refresh the browser page.
6. Run the workflow again.
7. Open the Python UDF operator and add a breakpoint. It now works properly.

https://github.com/user-attachments/assets/4d7b219f-7ada-4e82-a30c-9a033193aa54

### Version

1.1.0-incubating (Pre-release/Master)

### Commit Hash (Optional)

_No response_

### What browsers are you seeing the problem on?

_No response_

### Relevant log output

```shell

```

### Code of Conduct

- [x] I agree to follow Apache Code of Conduct

Reproduce the workflow sequence in a browser: create a workflow with a Python UDF operator, run it, and try to add a breakpoint before and after refreshing the page. Compare the debugger state across those steps; done means breakpoints can be added immediately after workflow creation without a refresh.

Written by the indexing model from the issue text.