Troubleshooting

100

User input validation error

This error indicates that the input provided by the user is incorrect in format, missing required fields, or the data does not meet validation criteria.

200

Identifier validation error

This error indicates a problem with a specific identifier, such as an application or deployment ID. It usually means the identifier is invalid or not recognised by the system.

300

Database failure

This error indicates a failure at the database level, often due to connection issues, query failures, or integrity constraints being violated.

400

Service failure

This error indicates a generic service failure, which could mean that an internal service is down, not responding, or has faulty service logic.

500

Utility failure

This error indicates a failure in utility functions or operations supporting the main service, such as helper functions or configuration loaders.

600

Downstream service failure

This error indicates a failure in a downstream service that the current service depends on, often due to issues with external API calls, third-party services, or microservices (Extensions, Neo Extensions, Shield).

700

Referrer validation error

This error indicates that the referrer, commonly used in HTTP requests to validate the origin of the request, is invalid.

800

Middleware validation error

This error indicates issues within the middleware layer, often related to authentication, authorisation, or preprocessing steps before the main service logic is executed.

Uncaught Error

Remote loaded successfully, but ushc_crm_4000084_membercareDev4000084_MFE could not be found! Verify that the name is correct in the Webpack configuration!

UAT or Prod mode for the application is not enabled and is currently running on localhost.