> ## Documentation Index
> Fetch the complete documentation index at: https://devdocs.xbox.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Types of error handling

> Common failure modes when calling XBOX Live services, including HTTP 400, 401, 403, and 503 responses, and how titles should catch and handle exceptions.

Take special care when making a service call.
Your title should always handle errors when making network calls.

Even for service calls that have been working consistently during development, service calls can fail in real-world environments for a number of different reasons.
For example, your call may fail because:

* The network is not available.
* The service is too busy, returning a 503 HTTP status code.
* The request is not valid, returning a 400 HTTP status code.
* The user does not have the right permissions, returning a 403 HTTP status code.
* The user has been banned, returning a 401 HTTP status code.
* The HTTP stack is unable to send the request (ERROR\_TIMEOUT, RPC\_S\_CALL\_FAILED\_DNE, etc.)

Most of these issues will result in an exception being thrown from the Services API layer.
Your title should capture these exceptions and handle them appropriately.


## Related topics

- [Marketplace Error Handling](/services/playfab/economy-monetization/economy-v2/marketplace/marketplace-error-handling.md)
- [SDK error handling Best Practices](/services/playfab/live-service-management/service-gateway/automation/cloudscript/sdk-error-handling-best-practices.md)
- [Handling common error cases](/services/playfab/multiplayer/matchmaking/error-cases.md)
- [Handling PlayFab Errors](/services/playfab/sdks/c/errors.md)
- [Handling Lobby and Matchmaking C++ SDK errors](/services/playfab/multiplayer/lobby/lobby-and-matchmaking-client-sdk-errors.md)