FAQ | This is a LIVE service | Changelog
It seems like this bug resulted from an incorrect merge into v3.