When Daemon is restarted or stopped, masternodes will show "not started", even though that's not the case. Once client is started up again after a couple of seconds it goes back to started, but we have seen in the past this is enough time for people to click the start button and end up not receiving rewards for 24+ hours.
Recommended solution: if daemon is not actually connected, either show a "connecting" message, or cache the "started message", not started should never be shown unless a masternode is actually not enabled.
oriz456
commented
5 years ago
When Daemon is restarted or stopped, masternodes will show "not started", even though that's not the case. Once client is started up again after a couple of seconds it goes back to started, but we have seen in the past this is enough time for people to click the start button and end up not receiving rewards for 24+ hours.
Recommended solution: if daemon is not actually connected, either show a "connecting" message, or cache the "started message", not started should never be shown unless a masternode is actually not enabled.