6 docs tagged with "errors"

\- The Redpanda streaming data platform is experiencing a severe, cascading failure.

The application is experiencing internal server errors when GraphQL operations attempt to access records that do not exist in the database. This occurs when GraphQL queries reference entities that have been deleted, were never created, or are inaccessible due to permission issues. Instead of handling these cases gracefully with proper error responses, the API is escalating them to internal server errors that may impact

The application is generating internal server errors during GraphQL operations due to uncaught exceptions in resolver logic. These errors are not properly handled or transformed into structured GraphQL responses, resulting in unexpected 500\-level failures for client applications. Stack traces often reference NestJS internal files like `external\-context\-creator.js`, indicating the framework attempted to execute resolver logic but encountered an exception that was not intercepted by the application code.

A deployment replica OOM caused HTTP 5xx error.

A session object in an application thread is possibly being accessed outside the scope of a request.

A Jetty HTTP 500 error occurred.