LH44:
Contact the support team, they should be able to manually sort this out for you. There have been a few reports of this. It should be resolve by version 1.5.5.3, but not sure about deployment yet :)
Last time I contacted the support team, they gave me little assistance, aside from try it again in a few hours. I'm not going to bother trying that again.