Thanks @UnborN for taking the time to pin point the issue
And thanks @LondonBenji for raising this issue.
Fixed in V1.5.7