To avoid the need for manual error code mapping, we propose a dynamic mapping that generates unique and deterministic error codes on the fly, encapsulating the context of an error in a single number (an error code). Additionally, we identify three categories of errors: WebSocket errors, some business logic errors, and database errors. When errors are propagated from one service to another, this approach simplifies logs by only transmitting the error code and potentially a customized error message, rather than duplicating the entire error object.