search

aws-samples / amazon-gamelift-ultrafrogroyale-large-match-sample

A small sample game that demonstrates how to use GameLift FlexMatch new large match features.
Apache License 2.0
22 stars 12 forks source link

Matchmaking ticket is in PLACING status and cannot be canceled. #1

Closed anshul90 closed 4 years ago

anshul90 commented 4 years ago

Hi Team, we've followed all the steps as per documentation to run the sample. But now we're facing an error in lambda of matchmaking failed. I'm attaching the screenshot of the error as well.

Error is like:

Error in Lambda assume matchmaking failed: {"message":"Matchmaking ticket is in PLACING status and cannot be canceled.","code":"InvalidRequestException","time":"2020-01-17T12:21:17.325Z","requestId":"499c4016-e005-4aa4-a164-b54cbbcb558c","statusCode":400,"retryable":false,"retryDelay":48.43038812741705}

UnityEngine.Debug:Log(Object)
GameNetworkManager:<FindMatch>b__12_0(AmazonServiceResult`2) (at 
Assets/GameNetworkManager.cs:154)
Amazon.Lambda.<>c__DisplayClass41_0:<InvokeAsync>b__0(AmazonWebServiceRequest, 
AmazonWebServiceResponse, Exception, AsyncOptions)
Amazon.Runtime.Internal.UnityMainThreadDispatcher:ProcessRequests()
Amazon.Runtime.Internal.UnityMainThreadDispatcher:Update()

image

Please help me out of it if you can. Thanks.

squidbot commented 4 years ago

Hi, sorry, my notifications aren't reaching me for some reason, I apologize for taking so long to response. I'm going to get in touch with the GameLift team to see if they can get you an answer more quickly than I can (I'm in GDC crunch mode alas.)

alanmur commented 4 years ago

Hello, So I think you are running the sample, then creating a match. Then when you create a second one, the fleet is out of capacity, because the first match hasn't ended, or isn't cleared up properly. I'm still trying to reproduce your issue, but running into some other things first. I'll get there, but try increasing the size of the fleet temporarily, and let me know if that confirms my diagnosis.

alanmur commented 4 years ago

Identified root cause (server process not terminating at the end of a game session), and testing a fix.