(if web-based) or restart the client application.
This is a status flag. In many systems, "extra quality" refers to a high-priority data verification check. The "2" usually indicates a specific failure state—often meaning "Data Mismatch" or "Incomplete Credentials." Common Causes (if web-based) or restart the client application
If the error persists across multiple users and different devices, it is time to contact your DevOps or IT Support team, as the "extra quality" check likely requires a server-side database re-indexing or an API patch. The "2" usually indicates a specific failure state—often
The "server response failed" part of the error often means the problem isn't on your end. Check your company’s IT dashboard or the service provider's status page. If the API gateway is down or under high load, you simply have to wait for the server to recover. 3. Verify Job Parameters If the API gateway is down or under
You may be running an outdated version of the client software that is sending requests in a format the updated server no longer recognizes. Step-by-Step Solutions 1. Perform a Hard Refresh and Re-authentication
If you have administrative access, look at the server-side logs for the timestamp of the error. Look for or HTTP 403 (Forbidden) . A 403 error specifically indicates that the "userstats" request failed because the user permissions have changed. Final Thoughts
Your login session has expired on the server side, but the client interface still looks active. When you try to pull user stats, the server rejects the request.