I set up 2 concurrent processes in a fleet like the picture below.
We needed 2 more dedicated servers. So I turned on a scaling policy like the picture below.
A couple of minutes after the scaling policy was turned on, we encountered this strange error like the picture below.
After the interruption, our matchmaking requests failed every time . So I just turned off the scaling policy and turn it on again and then we could submit our matchmaking requests to FlexMatch.
Why did it happen?
Just in case, I left the information.
FleetId : fleet-a520ea76-5989-474b-9915-8ca6b46dea2c
First GameSessionId : arn:aws:gamelift:us-west-2::gamesession/fleet-a520ea76-5989-474b-9915-8ca6b46dea2c/325a866e-6ba0-40c6-9a3e-aa2c776d567f
Second GameSessionId : arn:aws:gamelift:us-west-2::gamesession/fleet-a520ea76-5989-474b-9915-8ca6b46dea2c/83fcc5ad-e974-4e49-9f3c-52838592b3e7