Errors

Error Handling Guide

Understanding Application Errors

Errors are an inevitable part of any software application, and understanding how to identify, interpret, and resolve them is crucial for maintaining a robust system. In the NR Waste Plus application, errors are categorized and presented with specific error codes to help developers and users quickly identify the nature of the problem. Each error code follows a consistent pattern where the prefix letter indicates the error category. These codes are designed to provide immediate context about where the error originated and what type of issue occurred, enabling faster diagnosis and resolution.

Identifying Error Sources

When an error occurs in the application, the first step is to identify its source and scope. Frontend errors (F-series) typically manifest in the user interface and are often related to client-side validation, rendering issues, or browser compatibility problems. Backend errors, on the other hand, usually stem from server-side processing, database operations, or API communication failures. To effectively identify the error source, examine the error code, review the error message details, and check the application logs for stack traces or additional context. The error code structure provides valuable clues: for instance, a 404 error in the F-series (F404) indicates a forest client issue, while a G404 suggests a general resource not found at the server level. Understanding these patterns allows developers to quickly narrow down the problematic component and begin troubleshooting in the right area of the codebase.

Error Response Patterns

The application implements standardized error response patterns to ensure consistency across all layers of the system. Each error response includes multiple components: a unique error code, a human-readable message, a timestamp, and often additional metadata such as the affected resource or suggested actions. This structured approach to error handling enables both automated logging systems and human operators to process errors efficiently. Frontend components utilize these standardized responses to display appropriate user feedback, whether through toast notifications, error boundaries, or dedicated error pages. The backend services follow a similar pattern, returning HTTP status codes alongside custom error payloads that provide detailed information for debugging. This consistency in error handling across the stack ensures that errors can be traced from the user interface through to the underlying services, making it easier to identify patterns, track recurring issues, and implement comprehensive solutions.

Resolving and Preventing Errors

Effective error resolution requires a systematic approach that goes beyond simply fixing the immediate symptom. When addressing an error, developers should first reproduce the issue in a controlled environment, then analyze the root cause by examining relevant code paths, data states, and system configurations. Documentation of each error type, such as the dedicated pages for F404, G404, P403, R600, and U404, provides specific guidance on common causes and recommended fixes. Prevention strategies include implementing comprehensive input validation, adding defensive programming practices, establishing proper error boundaries in React components, and ensuring robust exception handling in backend services. Regular monitoring of error logs and metrics helps identify trends and potential issues before they impact users. Additionally, maintaining clear documentation of error handling procedures, conducting code reviews focused on error scenarios, and implementing automated testing for edge cases all contribute to a more resilient application that gracefully handles unexpected situations while providing meaningful feedback to users and developers alike.

When contacting support, please provide:

• The exact time the error occurred
• What you were trying to do when the error appeared
• Any error reference number shown on the screen
• The page or feature you were using