We are reviewing the issue now. Can you tell me if the problem corrected itself, or is this still on on-going issue?
Sorry for the very late response, I do believe the issue was fixed.
