Relicx streamlines session error and warning tracking by automatically categorizing issues and assigning default severities based on their nature. You can access the session errors by clicking on the errors tab on the session listing page.
At a fundamental level, these issues fall into two primary categories: Frontend errors and API errors.
Frontend errors typically manifest as uncaught exceptions, and they are automatically flagged with a critical severity level by default. In contrast, console errors are labeled as significant issues. Console warnings, which carry a low severity, remain hidden from view by default. To access these warnings, users must manually enable the "show low severity issues" toggle.
API errors follow a distinct classification system based on error codes. Errors with error codes falling in the 5XX range are deemed critical, signifying potentially severe disruptions in the system's functionality. Conversely, error codes outside this range are assigned a low severity, indicating issues that are less likely to severely impact the operation of the system. Notably, specific error codes such as 401, 403, and 404 are intentionally excluded from reporting to minimize extraneous noise in the error reporting.
API Error Code
Everything Else (Except 401,403 and 404)