I am currently using 2 instances of Node-RED (v1.2.9) in a production environment but when I try to save a flow or import a new flow from our testing environment there is an unusual behavior
I sometimes get "The flows on the server have been updated" even before I do any changes.
Workaround for this that I disable one of the running instances from PM2 and make changes and then again start the stopped instance to run the flow.
Is there any guide/documentation on how saving of flows work on a multi instance Node-RED setup and is this fixed in the recent versions??
Welcome to the forum @fuser
It is not completely clear what you are doing.
- Are the two node-red instances on the same machine or separate?
- If on the same machine are they completely separate or do they share the flow file, or anything else?
- In the browser are you sure you have only one tab open on each server at any one time?
- Have you got the node-red windows open on multiple PCs?
Do you mean you just randomly get that even though you have not touched anything?
If they are both using the same flows file, what is the difference between the two instances? Are they both running at the same time?
Are they running on different ports?
What exactly do you mean by 'startup'?
You said at the start that the workaround was to have only one running when you make changes, but now you say that it pops up even when no changes have been made.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.