How to debug an API 500 when the frontend only shows “Something went wrong”

When the frontend only says “Something went wrong,” start by connecting the user action to one request, one timestamp, and one request id.

The visible message is rarely enough. Open the browser network panel or client log and record the method, path, status, response body shape, and approximate time. If there are several failed requests, pick the first server-side failure rather than the cascade after it. A 401 followed by five 500-looking UI errors is a different problem from a clean authenticated request that returns 500.

Next, compare the input with a known working case. Check required fields, null values, uploaded file size, account state, feature flags, and whether the same action succeeds for another user. If the failing request has a request id, use it to find the server log line and copy only the relevant excerpt into a reproduction packet. Avoid pasting entire logs because the useful error is usually surrounded by repeated noise.

Then decide whether this is a request problem, data problem, dependency problem, or response parsing problem. A request problem fails before work begins. A data problem appears only for certain records. A dependency problem often clusters by time. A response parsing problem may show a successful backend result but broken client rendering.

The useful result is a short note another developer can run: action, request, input difference, timestamp, request id, and the smallest log excerpt that explains the failure.

How to debug an API 500 when the frontend only shows “Something went wrong”

// COMMENTS

ON THIS PAGE