Players briefly see entities from the previous instance after teleport

Having an issue where players are seeing entities from their old routing bucket right after being teleported to a new instance. The final routing bucket assignment is correct, but there's this brief window where they can see/interact with the wrong entities.

From my logs I can see the client teleport event is arriving before SetPlayerRoutingBucket executes on the server side. This seems to be timing-dependent especially under load - the teleport happens first, then the routing bucket gets set correctly afterward.

I initially thought this was an entity cleanup issue on my end, but the problem appears to be the sequence: teleport event hits the client while they're still in the old bucket, then the server moves them to the correct bucket after the fact. The end state is right, but that intermediate moment is exposing the wrong entities.

Anyone else run into this with OneSync routing buckets? Wondering if there's a way to ensure the routing bucket change happens atomically with the teleport.