Thanks very much for making a repro Colin - that will help us pin this down. Very much appreciated.
Can I bother you to raise an issue please? Don't wanna let it slip under the radar.
Ofc, thanks also to @paulkeates for highlighting it originally.
I will submit an issue, I am doing a bit more investigation first. Surprisingly it appears not to be an issue specifically with the beta version, I am seeing the same problem on 3.0.2
@paulkeates what version did you upgrade from?
Ah, V3.0.2 does not support the catch within group option. Importing the sample flow to 3.0.2 does give the same error, but it would not be expected to work properly anyway.
Issue submitted Catch "in same group" in subflow shows errors in log and does not work · Issue #4292 · node-red/node-red · GitHub
1 Like
I'm still seeing the sidebar default to the wrong tab on reload of the Editor
In the live version, that would default to the debug (1st) tab. Now it always defaults to the i tab which is super annoying.
did you drag/move the i tab to front?
what happens if you drag/move the 
to 1st place & refresh.
Sorry, I should have said explicitly, if you look at the image, I've already rearranged the tab icons. Debug is already at the start, that's how I noticed the issue. I always put my tabs in that order.
No matter what order I put them in, a page reload always makes i show, not the last selected nor the 1st tab (which was the previous default I believe). Actually the previous default was that the last selected tab is shown after a reload.
What browser are you using and have you tried another?
Lastly, could you check the local storage before / after changing tab, before / after refresh.
I use Edge by default. Happens with Vivaldi and with Firefox as well.
Local storage before page reload:
Changes back to:
While the page is loading (with the progress bar still showing).
Then we might have a lil' buglet! Would you be kind enough to raise an issue Julian?
1 Like
1 Like
Not sure what it does, but entering a Client ID number in the MQTT broker settings fixed the misconfigured server warning triangle for me.
Does it stay fixed if you refresh the browser page?
Also are you using the beta version?
Yes and yes. I noticed it would highlight the client ID box in red, so maybe the auto generate bit is not working when blank?
1 Like
You are correct. If a client ID is specified then the problem is not seen. I will add that to the issue. Thanks.
1 Like
Another slight issue that I've not seen in previous versions of Node-RED.
With the current beta, if I change the output status for a debug node - say from no output to output - but do not re-deploy. If I've been away from the Editor for a while and come back, the debug node does not output anything though it should do because that is its current status even though it hasn't been deployed.
I'm pretty sure this used to work?
Your right - the button should start/stop debug output without need to deploy
And just checked on my beta install and it still does
You need to leave it for some time - maybe let the PC go to sleep and then wake it up again.
Does the blue dot stay there? I am wondering whether the page is reloading.
Yes, the blue dot and the red deploy button both still remain.
