This has occurred due to a bug that is currently being investigated. If you do see this please contact support and provide this KB article to have this issue corrected.