Ahh good catch. I fixed in on our development copy, we will release the fix in the next update.

Thanks for catching that.