Roaming issues on Unleashed 200.19

[Alleprt]

It's been a while since I updated Unleashed to 200.19. Over this time, I noticed these intermittent issues. Background: I have three R750 APs. The band is 5 GHz. Encryption - WPA3-SAE. The device is the Pixel 9 Pro. All kinds of access/admission controls, load/band balancing are disabled. 802.11r FT Roaming, 802.11k, background scanning are enabled. OFDM Only is enabled. BSS Min Rate is 12.00 Mbps. 

Sometimes, when I move around, I notice my phone loses its WiFi signal and is left on cell service only. I look at the WiFi setting and see that it is trying to connect to WiFi but is stuck in "obtaining IP" status, then it gives up and stays on LTE/5G. I click on the SSID, and it connects to the AP with about 50% signal strength, then it quickly roams to the nearest AP with about 100% signal strength, and it loses connectivity, i.e., Android shows that it's connected to WiFi, but sites don't open, the Ruckus app can't connect, etc. There is no traffic on the WiFi. At this moment, I had a chance to look at the status in Unleashed from my PC and saw that Auth Method for this phone was listed as Open FT. 

Googling helped me find out that Open FT means that the client just roamed from another AP, which is what I observed just before that. So, it looks like the AP with the highest signal was blocking traffic to my phone that had just roamed to it. Android detected it, disassociated, switched to LTE/5G, tried again, connected to the lower-signal AP, and quickly roamed to the AP with better signal. At that moment, I discovered that there was no traffic on the WiFi before Android disassociated again. Somehow, later, the phone connected to the same AP with the highest signal, and all was well. But at the beginning of roaming, that particular AP was blocking traffic for some reason. 

I had noticed several times before that my phone suddenly switched to LTE/5G when I was inside a house with 3 APs nearby. I don't think it had been happening before I upgraded to 200.19. 

I wonder if you have had other reports like this or if you can reproduce it in the lab. The traffic block happens in the first 30-60 seconds after a client roams to the AP.