![]() ![]() There is very little a game can do to handle these errors. It is possible to also get these when internet routing between the client and PlayFab's servers are disrupted for some reason. The most common source is a disconnection on the client side. These all are indicative of networking issues. Calls to get the list of players in a segment would be the key thing to examine (a task targeting a segment also causes re-evaluation, but that should be infrequent).ĭepending on the specifics of the SDK you're using and the underlying networking stack, it is possible to see errors such as ConnectionError, ConnectionTimeout, or other errors related to difficulties contacting the PlayFab servers. How frequently you're calling CloudScript per player.How often your script calls utilize near-maximum time per call (or worse, time out).For the former, the two things to examine are: Your title is either hitting CloudScript too hard, or is trying to force segment evaluation too frequently (or both). These codes only occur on specific API methods (listed on the documentation page for those methods), but if you see them, there are important consequences of which you should be aware. Evaluate the returned error details to determine which limit would be exceeded. Indicates that an attempt to perform an operation will cause the service usage to go over the limit as shown in the Game Manager limit pages. Indicates that the URL for this request is not valid for this title. Postman is a useful tool for debugging this situation. Otherwise, report the error on the forums, with your titleId, the full request JSON (if possible), and the error output. To resolve this, experiment with your inputs, and try to determine if your inputs are invalid in some way. This typically occurs if bad information is sent to a third-party add-on, and our server experienced an unknown result or error while interacting with external systems. This title has been deleted from PlayFab, and can no longer be used. Probably a typo, or you've got a bad input somewhere. This method has been disabled by the API Policy, and cannot be called.Īttempted to access an entity (player, character, title, etc.), which does not exist. Incorrect credentials, or otherwise bad inputs related to logging in. The client has tried to call an API that requires SessionTicket authentication, without logging in first. In the admin API, explicit TitleIds are a Dev-> Test-> Live safety feature. In most SDKs, you should not specify a TitleId for login requests, as it is done for you. The request provided a TitleId which does not match the title provided in the URL of the method. The API request object sent to PlayFab is invalid and cannot be executed. The API request object sent to PlayFab has invalid parameters and cannot be executed. The entity type in the token used for authentication is not supported by this API. If you're making your own raw HTTPS calls to PlayFab API methods, your Content-Type header must be application/json. It should be impossible to get this if you're using one of our SDKs. This error will always occur if the identifier is not correct.Īll API requests have been disabled for this title, and it can no longer be used. The player account does not exist, likely because you are not copying a PlayFabId/TitlePlayerId correctly. The player account has been deleted, all API methods will fail with this error. The player account has been banned, all API methods will fail with this error. Most specific codes listed with an API method also fall into this category. If you get these error codes, you should never retry, because the request can never be completed under the current circumstances without a bug-fix or setting change. If you do retry this request, is is important to properly use an exponential backoff strategy. Indicates that PlayFab may be having a temporary issue or the client is making too many API calls too quickly. Indicates that PlayFab or a third-party service might be having a temporary issue. Indicates too many simultaneous calls, or very rapid sequential calls. Indicates too many simultaneous calls or very rapid sequential calls. Indicates too many calls in a short burst.ĪPIConcurrentRequestLimitExceeded (1342): These errors typically mean that your client is making calls too quickly, but the request itself may be valid.ĪPIClientRequestRateLimitExceeded (1199): It is usually safe to retry requests that fail with these error codes, with an exponential delay back-off. If the error code you are looking for is not available on this page, see our more general http response status code guidance. This page lists the common error codes that you might encounter. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |