So after a good weeks worth of testing and messing with the TickTime like suggested, I am still getting a lot of these messages.

Code
!Getting websocket token...
!PRIVATE: readloop_handler: stream truncated
!Websocket connected to wss://ws.kraken.com/
!Websocket connected to wss://ws-auth.kraken.com/
!Kraken server version: 1.8.8, status: online
!Kraken server version: 1.8.8, status: online
!PRIVATE: readloop_handler: stream truncated
!Getting websocket token...
!Websocket connected to wss://ws.kraken.com/
!Websocket connected to wss://ws-auth.kraken.com/
!Kraken server version: 1.8.8, status: online
!Kraken server version: 1.8.8, status: online
!PRIVATE: readloop_handler: stream truncated
!Getting websocket token...
!Websocket connected to wss://ws.kraken.com/
!Websocket connected to wss://ws-auth.kraken.com/
!Kraken server version: 1.8.8, status: online
!Kraken server version: 1.8.8, status: online

[365: Fri 21-09-24 15:40] 44165.60/45165.30\40766.90/41827.80 -11.40
Exit  XBT/USD  0
!PUBLIC: readloop_handler: stream truncated
!PUBLIC: readloop_handler: stream truncated
!PUBLIC: readloop_handler: stream truncated
!Getting websocket token...
!Websocket connected to wss://ws.kraken.com/
!Websocket connected to wss://ws-auth.kraken.com/
!Kraken server version: 1.8.8, status: online
!Kraken server version: 1.8.8, status: online
!PRIVATE: readloop_handler: stream truncated
!PUBLIC: readloop_handler: stream truncated
[366: Sat 21-09-25 15:40w] 41827.70/43200.00\41659.50/42668.20 -0.10
Exit  XBT/USD  0


It seems like it still disconnects and has trouble, I am not sure if this could potentially put the Zorro in a bad state or miss a trade. I changed the TickTime to what you suggested and then reduced it even more testing it further. Repeated this up to TickTime = 100.

Last edited by Arkom; 09/25/21 23:38.