It is an API bug, but I got no clear information about its reason. I think that it will be gone with the next FXCM API update.