We've been using the matchmaker successfully in a development environment: game client sends a Matchmake request, then the client connects to the PlayFab managed game server instance and the server then successfully calls RedeemMatchmakerTicket with the lobby ID from the game server instance's command line parameters and the ticket sent by the client.
This has been working tor the past few months, and has been working for the current client+server build too, but since yesterday we're having an issue. The game server starts up correctly and the client connects, but when the server calls RedeemMatchmakerTicket that call returns GameNotFound. I verified that the correct lobby ID is still passed in (command line parameter game_id decimal string) and that the game client's matchmaker ticket is is received correctly on the game server. For example:
LobbyID = 8302156743495296161
Ticket = 3BD3828D5E76118-0-E4CD2263A259D1E6-ED9D-8D4B2542FB0D431-6CA8E3303E21C3B7.17AEA0BA6B32CBBB
The client can still join the game server, but right now we can't successfully redeem the ticket to let the matchmaker know that the client has connected. Because we've used the matchmaker successfully with the current build of the game and the issue started appearing while using the same build, I wonder if anything has changed on the backend that is causing this behavior.
Any information about what can trigger GameNotFound is appreciated too. I read in related questions that it triggers when the lobby ID and ticket pair don't match. I've checked that this issue happens with a freshly restarted client in his first and only Matchmake request, so it isn't an old ticket. Our Max instances per host is set to 1, so its not connecting to another lobby on the same machine.
Lastly, a recent change is that we've started testing with multiple servers. However, I don't think the Matchmake call will return the IP of one server, but with a ticket for a lobby on a different server.
Any ideas are appreciated! Thanks in advance,
Zhi Kang Shao
