Open kylerberry opened 6 years ago
The issue here is definitely with closing my laptop and opening it hours later. This could also happen if the websocket closes and takes a long time to reconnect. The historic data is then too stale and causes signal values to be incorrect. Not sure if there should be a fix for this yet.
I'll leave as an enhancement to fetch fresh historic data after an interruption
Bot stops signaling anything over time.
Possible causes: