If the internet connection on the host machine is lost temporarily, like a minute, arby does not successfully issue new orders on restart. Since this could be because of non-significant price changes on CEX side, I am leaving the environment running to see if it starts issuing orders at some point. EDIT: not in the 2h I observed it.
What we want to do eventually is: force new order issuance after price stream loss + recovery.
Slightly bumping prio. Experienced this today with a simple xud upgrade+restart. Took me a moment to remember that I need to wait for the next price change for new orders to be issued.
If the internet connection on the host machine is lost temporarily, like a minute, arby does not successfully issue new orders on restart. Since this could be because of non-significant price changes on CEX side, I am leaving the environment running to see if it starts issuing orders at some point. EDIT: not in the 2h I observed it.
What we want to do eventually is: force new order issuance after price stream loss + recovery.