This is now fixed - thanks very much for reporting, and please let us know if you see any further issues!