DPR is aware of that issue. Thought he might be fixing it during maintenance. Is it still giving the same error?