Got it, it's a bug and happens because of the token calculation. We'll fix it. Thanks for reporting.