Description
An HTTP 500 server error was returned from the external service NEH (Nordisk E-handel). The error indicates a server-side problem and that the request could not be completed.
Common causes
Temporary outage or maintenance at NEH.
Timeout or failure in a downstream subsystem at NEH.
Unexpected server bug triggered by the submitted data (e.g., unusual combination, large payload).
High load/resource exhaustion resulting in a generic 500 response.
Network disruption between the integration and NEH.
Resolution
Check status/logs: see whether other calls are receiving 5xx at the same time. Note the timestamp, any request/trace IDs (e.g., X-Request-Id, Trace-Id), and the endpoint.
Retry later if 5xx persists for several minutes.
Tips
5xx = server side (retry), 4xx = client side (fix data/permissions).
Distinguish 500 from 502/503/504 (gateway/unavailable/timeout) in alerts and retry policy.
Comments
0 comments
Please sign in to leave a comment.