You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Click the down arrow menu on the "Deploy" button in the upper right corner of the Node-Red interface
Select "Restart Flows"
What happens?
The flow does not restart, and instead the error "Deploy failed: {"code":"unexpected_error","message":"runtime.flows.loadFlows is not a function"}" is shown in the popup area that appears at the top of the screen in the middle.
What do you expect to happen?
Previously, the "Restart Flows" option has worked as expected, restarting my flows when clicked.
Please tell us about your environment:
Reproduced in two separate Node Red instances using both the RPi Chromium browser on the server itself and Safari from an independent Mac on the same network. The two node red instances have different sets of third-party nodes installed, but do have at least two in common: node-red-contrib-node-lifx, and node-red-contrib-darksky.
Node-Red Server 1 =====
Node-RED version:
v1.2.1
Node.js version:
v12.19.0
npm version:
v6.4.18
Platform/OS:
Raspberry Pi (3B+)
Browser:
Chromium on same host as Node-Red, Safari on Mac on same network
Node-Red Server 2 =====
Node-RED version:
v1.2.1
Node.js version:
v12.19.0
npm version:
v6.4.18
Platform/OS:
Raspberry Pi (4B - 4GB)
Browser:
Chromium on same host as Node-Red, Safari on Mac on same network
The text was updated successfully, but these errors were encountered:
What are the steps to reproduce?
What happens?
The flow does not restart, and instead the error "Deploy failed: {"code":"unexpected_error","message":"runtime.flows.loadFlows is not a function"}" is shown in the popup area that appears at the top of the screen in the middle.
What do you expect to happen?
Previously, the "Restart Flows" option has worked as expected, restarting my flows when clicked.
Please tell us about your environment:
Reproduced in two separate Node Red instances using both the RPi Chromium browser on the server itself and Safari from an independent Mac on the same network. The two node red instances have different sets of third-party nodes installed, but do have at least two in common: node-red-contrib-node-lifx, and node-red-contrib-darksky.
Node-Red Server 1 =====
v1.2.1
v12.19.0
v6.4.18
Raspberry Pi (3B+)
Chromium on same host as Node-Red, Safari on Mac on same network
Node-Red Server 2 =====
v1.2.1
v12.19.0
v6.4.18
Raspberry Pi (4B - 4GB)
Chromium on same host as Node-Red, Safari on Mac on same network
The text was updated successfully, but these errors were encountered: