Module aws_sdk_gamelift::types::error

source ·
Expand description

Error types that Amazon GameLift can respond with.

Modules§

Structs§

  • The requested operation would cause a conflict with the current state of a service resource associated with the request. Resolve the conflict before retrying this request.

  • The specified fleet has no available instances to fulfill a CreateGameSession request. Clients can retry such requests immediately or after a waiting period.

  • The game instance is currently full and cannot allow the requested player(s) to join. Clients can retry such requests immediately or after a waiting period.

  • A game session with this custom ID string already exists in this fleet. Resolve this conflict before retrying this request.

  • The service encountered an unrecoverable internal failure while processing the request. Clients can retry such requests immediately or after a waiting period.

  • The requested operation would cause a conflict with the current state of a resource associated with the request and/or the fleet. Resolve the conflict before retrying.

  • The requested operation would cause a conflict with the current state of a resource associated with the request and/or the game instance. Resolve the conflict before retrying.

  • One or more parameter values in the request are invalid. Correct the invalid parameter values before retrying.

  • The requested operation would cause the resource to exceed the allowed service limit. Resolve the issue before retrying.

  • THe requested resources was not found. The resource was either not created yet or deleted.

  • The operation failed because Amazon GameLift has not yet finished validating this compute. We recommend attempting 8 to 10 retries over 3 to 5 minutes with exponential backoffs and jitter.

  • The specified game server group has no available game servers to fulfill a ClaimGameServer request. Clients can retry such requests immediately or after a waiting period.

  • The requested tagging operation did not succeed. This may be due to invalid tag format or the maximum tag limit may have been exceeded. Resolve the issue before retrying.

  • The service is unable to resolve the routing for a particular alias because it has a terminal RoutingStrategy associated with it. The message returned in this exception is the message defined in the routing strategy itself. Such requests should only be retried if the routing strategy for the specified alias is modified.

  • The client failed authentication. Clients should not retry such requests.

  • The requested operation is not supported in the Region specified.