A matchmaking ticket stays “InProgress” until Matchmaker can add the server’s connection information. With Cloud Code hosting, that only happens after your allocator’s Poll function returns Allocated.
Issue:
Unity Matchmaker ticket status remains at "InProgress" and does not update to "Found" even though the server was successfully allocated.
The ticket status returned by MatchmakerService.Instance.GetTicketAsync() doesn't change from "InProgress" to "Found".
Environment:
- Matchmaker tickets are successfully created and stored
- The server is allocated correctly with an Allocation ID
- GetTicketAsync() is being polled properly
Cause:
Matchmaker calls your allocator’s Poll function every 2 seconds. While Poll returns Pending, the ticket’s status stays "InProgress". The ticket is only updated when Poll returns Allocated with assignment data such as the IP and port. If Poll keeps returning Pending, for example because it’s waiting for a server-ready signal that never arrives, the ticket stays "InProgress". If the allocation fails or times out, the ticket’s status changes to "Failed".
Resolution:
- Check that your allocator’s Poll function returns
PollStatus.AllocatedwithAssignmentDataonce your hosting provider reports the server as ready. If your hosting provider requires the game server to signal that it’s ready, make sure your server does this after it finishes starting up. - Check the Matchmaker logs for allocation errors.
- Use Multiplayer Services 2.1.0 or later, and make sure that your polling code checks the ticket’s status. Pending and failed tickets both use the
Noneassignment type, so the assignment type alone can’t tell them apart.