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 error identifies a "job request." If you are trying to pull stats for a specific task or report, ensure that the job ID still exists. If a job was deleted or archived while you were trying to view its stats, the server will return a failure because it cannot find the data associated with that ID. 4. Disable VPN or Proxy If the error persists across multiple users and
Are you seeing this error within a like an ERP or a cloud-based dashboard? Look for or HTTP 403 (Forbidden)
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 If the error persists across multiple users and
(if web-based) or restart the client application.
This identifies the specific function being called. The system is trying to request "User Statistics" related to a specific "Job" or task via the API.