I've seen a couple of cases where queryNodeStatus returned by Argus /status endpoint was stuck and not updating anymore even though the QN itself was available and updating. My guess is that the subscription is set up only once and if it breaks for some reason, it's never reconnected so the node is stuck with past QN state until restart. At some point we should verify that this is happening, and if yes, add some kind of reconnect
I've seen a couple of cases where
queryNodeStatusreturned by Argus/statusendpoint was stuck and not updating anymore even though the QN itself was available and updating. My guess is that the subscription is set up only once and if it breaks for some reason, it's never reconnected so the node is stuck with past QN state until restart. At some point we should verify that this is happening, and if yes, add some kind of reconnect