Ambiguous JSON retry value in history queue
Posted: June 8th, 2024, 7:02 am
Sabnzbd 4.3.2 api :
When an item moves to the history queue the value of 'retry' is shortly false but then, after a moment it changes to 0.
My deserializer cannot handle a boolean which is suddenly an integer.
When an item moves to the history queue the value of 'retry' is shortly false but then, after a moment it changes to 0.
My deserializer cannot handle a boolean which is suddenly an integer.