Was unsure what to tag this with, so apologies if it’s in the wrong place.
For character concurrency, I understand it as not necessarily meaning you can’t have more than the “Character concurrency limit” sessions running, but that it only allows for that number of API calls/interactions to happen at the same time - correct?
What happens when you reach this limit, if too many requests are being sent at the same time? Will they fail, and is there any way of figuring out exactly what went wrong, to react on it? Will the characters simply not respond, will they just take longer to respond (waiting for the other requests), or will the session fail entirely?
You’re correct. Character concurrency refers to the maximum number of users who can interact with an NPC simultaneously. It limits how many interactions can occur in parallel.
If the concurrency limit is exceeded, additional requests will fail. The character will not respond to those requests, and they will not queue or delay. Instead, the session will return an error.
You can find more detailed examples at the bottom of our Pricing Page.
Thank you @K3 !
I don’t suppose there’s any way as of now to see when a failure is actually due to the concurrency limit? Would be very helpful to get some sort of error code in UE when it does fail, for our own logging and potentially showing info to our end users.