We have successfully resolved the incident that caused some users to experience a Version Mismatch.
Any remaining tickets for caching/connection issue for specific users will be investigated individually.
We appreciate your patience and understanding throughout this process.
Dec 7, 16:26 PST
Some individual users are still experiencing connection issues.
The common denominator is after clearing their cache and trying multiple browsers, eventually one will let them in.
Our team is documenting and comparing tickets for this unique issue.
Dec 7, 14:27 PST
We are seeing a healthy recovery for the customers affected.
As you are accessing if your system is still having connection issues, please test your URL in a different type of browser.
We have seen caching contribute to the issue.
Dec 7, 13:03 PST
Some customers are recieving a 503 error. We are implementing a fix for this.
**As a note it has been reported that at the same district one user gets a 504 or 503 error, while others are able to work as normal. We appreciate the information and are taking it into account to resolve the full issue.
Dec 7, 10:27 PST
Some customers are recieving a 504 error/timeout error.
This is a side effect of the resolution and we apologize for the inconvenience.
Dec 7, 09:12 PST
As we are implementing a resolution customers may experience some latency.
Dec 7, 08:48 PST
We have identified the issue and have implemented a resolution.
Dec 7, 08:14 PST