Handling HTTP 500

Provides guidelines for addressing server errors (HTTP 500).

Error Code	Error Reason	Suggested Handling Method
500 - Internal Server Error	A generic error message is provided when an unexpected condition is encountered and no specific message applies.	Implement a retry strategy to determine if the 500 error is a random occurrence. Once you've established that the error is not random, verify the validity of the request. If you still believe the request is valid, contact our Application Operations team for assistance.
501 - Not Implemented	The server does not recognize the request method or lacks the ability to fulfill the request, often implying that future availability may be expected (e.g., a new feature in the web-service API).	Fail the request and check whether the request is currently supported by the web service associated with this endpoint.
502 - Bad Gateway	The server acts as a gateway or proxy and receives an invalid response from the upstream server.	For this, implement a retry strategy that accommodates high load situations. We suggest using an "Exponential Backoff" strategy, as follows: 5 seconds → 10 seconds → 20 seconds → 40 seconds → then every minute until a defined timeout. We recommend a timeout of at least 30 minutes from the initial request. Once the timeout is reached and the message has failed, please contact our Application Operations team for assistance.
503 - Service Unavailable	The server is currently unavailable due to being overloaded or undergoing maintenance. This condition is typically temporary.	For this, implement a retry strategy that accommodates high load situations. We suggest using an "Exponential Backoff" strategy, as follows: 5 seconds → 10 seconds → 20 seconds → 40 seconds → then every minute until a defined timeout. We recommend a timeout of at least 30 minutes from the initial request. Once the timeout is reached and the message has failed, please contact our Application Operations team for assistance.
504 - Gateway Timeout	The server, acting as a gateway or proxy, did not receive a timely response from the upstream server.	For this, implement a retry strategy that accommodates high load situations. We suggest using an "Exponential Backoff" strategy, as follows: 5 seconds → 10 seconds → 20 seconds → 40 seconds → then every minute until a defined timeout. We recommend a timeout of at least 30 minutes from the initial request. Once the timeout is reached and the message has failed, please contact our Application Operations team for assistance.
505 - HTTP Version Not Supported	The server does not support the HTTP protocol version specified in the request.	Fail the request and verify that the client making requests to pmsXchange is configured correctly.