This problem has been corrected for the second time. Hopefully the reasoning will be fixed. Tech support is unsure of the cause but is looking into it.