javier, this is a display error and has been fixed in 3.0.5, just released earlier this evening. Pavlos, you'd need to open a support ticket (or have your host do so if you're an end-user) as we'd need to investigate the account in question and see what you're referring to.