Avability Monitor doesn't create routes every time #604
Description
Is your feature related to a problem?
When we start AM after making sure that there are nodes in the DB listed we get: pairIds: [(none)]
2023-12-13T12:20:52.018Z rpch:availability-monitor:info AM[v1.0.2] running with { connectionString: '<redacted>' }
2023-12-13T12:20:52.094Z rpch:availability-monitor:availability:info updated zerohops with pairIds: [(none)]
2023-12-13T12:20:52.095Z rpch:availability-monitor:availability:info updated onehops with pairIds: [(none)]
2023-12-13T12:20:52.095Z rpch:availability-monitor:availability:info scheduling next run in 9m52s
2023-12-13T12:21:04.522Z rpch:availability-monitor:info AM[v1.0.2] running with { connectionString: '<redacted>' }
2023-12-13T12:21:04.592Z rpch:availability-monitor:availability:info updated zerohops with pairIds: [(none)]
2023-12-13T12:21:04.593Z rpch:availability-monitor:availability:info updated onehops with pairIds: [(none)]
2023-12-13T12:21:04.593Z rpch:availability-monitor:availability:info scheduling next run in 1m0s
2023-12-13T12:21:22.539Z rpch:availability-monitor:info AM[v1.0.2] running with { connectionString: '<redacted>' }
2023-12-13T12:21:27.135Z rpch:availability-monitor:info AM[v1.0.2] running with { connectionString: '<redacted>' }
2023-12-13T12:21:30.393Z rpch:availability-monitor:info AM[v1.0.2] running with { connectionString: '<redacted>' }
2023-12-13T12:21:33.533Z rpch:availability-monitor:info AM[v1.0.2] running with { connectionString: '<redacted>' }
2023-12-13T12:21:38.646Z rpch:availability-monitor:availability:info updated zerohops with pairIds: 6/6 routes over 2 entries e.mYQA>3x:x.MGe2_x.oiLe_x.6D7d,e.iJpc>3x:x.MGe2_x.oiLe_x.6D7d
2023-12-13T12:21:38.650Z rpch:availability-monitor:availability:info updated onehops with pairIds: 6/6 routes over 2 entries e.mYQA>3x:x.oiLe_x.6D7d_x.MGe2,e.iJpc>3x:x.oiLe_x.6D7d_x.MGe2
2023-12-13T12:21:38.651Z rpch:availability-monitor:availability:info scheduling next run in 9m43s
It seems that sometimes there are some errors on getting the nodes from the DB which cause not finding pairs.
Restarting AM doesn't always help. We can see that in the example above.
Maybe we should add some check for reason why we do not see nodes and if its 1 of the 1st runs, make it more frequent untill we find pairs?