Thanks for spotting this!  Fixed this bug in development and will deploy soon.