Moritz Klack

I am glad you could solve this @noams-unbiased. Let me know if you have any further information here @tim-field. I hope we can fix it for your use case too!

@tim-field the issue is, that you are working with a controlled flow but don't apply the changes correctly. It would be better, if you could always apply the changes (this...

Please re-open if the issue still persists.

Fixed in React Flow 12! If you are using 11, you can find the migration guide here: https://reactflow.dev/learn/troubleshooting/migrate-to-v12

Please re-open if the issue still persists.

I understand that this is a bit confusing, but I don't have a better idea. I would not like to introduce another callback that would be needed to sync the...

I thought about this again, and I still don't have a better idea. We support uncontrolled flows without the need of using `onNodesChange`/ `onEdgesChange` and controlled flows, where you are...

> This might be helpful -> https://reactflow.dev/docs/guides/troubleshooting/#warning-seems-like-you-have-not-used-zustand-provider-as-an-ancestor, I had a similar issue when calling `useReactFlow`. That link answers the question. It's a React Flow issue and can be closed!

I tried it locally :) That's why I am asking. You could plug it into netlify or something similar for now.

got it! Thanks for the reply.