We are excited to announce that we have launched our new Hive Community! HiveNation will remain as an archive, but all new posts, discussions, and articles will be created on Hive Community. You can visit our new community at thehivecommunity.aerohive.com
This sounds to me like there may be an intervening NAT device, typically a firewall, that has too short of an inactivity timer on it's pseudo-session timer for UDP traffic. The AP connects, the FW ages out the NAT-mapping, the next CAPWAP frame from the AP fails to get delivered while a new session gets established in the FW, and wash, rinse, and repeat.