Kelly Bennett suggested an idea · Mar 18 at 03:00 AM · CloudScript
I have created an API layer with Azure Functions which responds with various status codes, but those status codes are not visible to the client when wrapped by ExecuteFunction.
For example: Say I have an Azure Function which returns an HTTP Status Code 429 when it's hit too frequently.
From PostMan I can verify that the endpoint does indeed return a 429 when I spam it like crazy
However, when I register that Azure Function with PlayFab and use PostMan to hit the Azure Function through ExecuteFunction, I never see a 429. Instead I see the same response that I see for all non-200 responses
{ "code": 400, "status": "BadRequest", "error": "CloudScriptAzureFunctionsHTTPRequestError", "errorCode": 1473, "errorMessage": "Invocation of cloud script function <Function Name> failed" }
My Client can not use this response to know to slow down polling my API, for example.
It would be very useful for ExecuteFunction to pass along the underlying HTTP status code so that clients can use those codes (or log them).
We would love to know what you need. Submit your ideas and upvote others to help us prioritize.
GitLab integration for CloudScript Content Management
Update the Server API to allow UpdateUserTitleDisplayName
CloudScript - Include commit header beside the version #
Change User display name via Server API / Cloud Script
Improve GrantItemsToUsers to support item grants from multiple catalogs in a single call
Matchmaking rule type: CloudScript (Azure Function) for custom MM logic
Internal code editor for cloud scripting
cloudscript tasks on player segments should tally OKs and Fails