Switch node not Consistent

recently i noticed that my flows were not getting executed consistently. i did an analysis and found that it was switch node that was creating the problem. it works inconsistently. some times it forwards the input and at times it remains idle. it is messing up almost all my flows..and when i deleted the node and made a new one just as the deleted one,it works..any advises?

First tell us what hardware and operating system you are running on, then show us the node-red startup log you get from restarting node-red, starting with the Welcome to node-red message.

I am running node red from my hassio system which is running in orange Pi PC 2. is this the log you have asked for.

Welcome to Node-RED
===================
6 Jun 19:27:33 - [info] Node-RED version: v0.20.5
6 Jun 19:27:33 - [info] Node.js  version: v10.14.2
6 Jun 19:27:33 - [info] Linux 4.19.13 arm64 LE
6 Jun 19:27:35 - [info] Loading palette nodes
6 Jun 19:27:49 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
6 Jun 19:27:50 - [info] Dashboard version 2.15.4 started at /endpoint/ui
6 Jun 19:27:54 - [info] Settings file  : /etc/node-red/config.js
6 Jun 19:27:54 - [info] Context store  : 'default' [module=memory]
6 Jun 19:27:54 - [info] User directory : /config/node-red/
6 Jun 19:27:54 - [warn] Projects disabled : editorTheme.projects.enabled=false
6 Jun 19:27:54 - [info] Flows file     : /config/node-red/flows.json
6 Jun 19:27:54 - [info] Server now running at http://127.0.0.1:46836/
[19:27:54] INFO: Starting NGinx...
6 Jun 19:27:55 - [info] Starting flows
nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)
6 Jun 19:27:57 - [info] Started flows
6 Jun 19:27:57 - [info] [mqtt-broker:Mosquitto] Connected to broker: mqtt://192.168.33.250:1883
6 Jun 19:27:58 - [error] [alexa-home-conf:ba964fdb.7ae7a] Error: connect ECONNREFUSED 34.240.81.189:8883
6 Jun 19:27:59 - [error] [api-call-service:Isha prayer Time] Call-Service attempted without connection to server.
6 Jun 19:27:59 - [error] [api-call-service:TV Mute] Call-Service attempted without connection to server.
6 Jun 19:28:00 - [info] [server:Home Assistant] WebSocket Connected to http://hassio/homeassistant

When you say it remains idle do you mean it is not passing on some messages? If so have you got an Otherwise output on the node? If not then add one and put a debug node on it and see if anything appears.
If still no joy then show us the config for the switch node and put debug nodes on the input and outputs of the Switch node and show us which messages it is misbehaving on.

By idle i mean that the message is not sent through at times. Some time the message is transferred through. So there is complete inconsistency. When I am designing the flow the switch would be working perfectly even in testing. but afterwards it fails to sent messages through. i have checked with inject node and debug node at input and output respectively with affected switch node. during testing it fails. Then i deleted the node and made a node with the same characteristics. at that time it worked.

You have only answered the first question in my post. Remaining to be answered:
Have you got an Otherwise output on the node? If not then add one and put a debug node on it and see if anything appears.
If still no joy then show us the config for the switch node and put debug nodes on the input and outputs of the Switch node and show us which messages it is misbehaving on.

@sheminasalam Isn't it the ui_switch node you are referring to? (Just to clear things up :smiley:)

Tried Otherwise rule and it worked for now.If i spot anything odd, will get back you.

Yes.....its the thing

What thing? You replied that adding the Otherwise rule worked, which implies it is a Switch node, but your latest posts suggests it is a dashboard ui_switch node, not a Switch node.

sorry i said its the switch node...pardon for being in-discrete. its switch node only not dashboard ui switch