Can't get ZT Gateway/Warp Managed Network Beacon to work

I've recently been trying to move our internal company ops to cf warp/gateway but have been having some difficulties with some features, namely, I can't get the "Managed Network" beacon feature to work. The goal was to disable warp dynamically when someone is physically at the office, using the profiles system, so that they can connect to local resources over local network without being routed through tunnels/public internet (making latency slightly lower). I followed this guide: https://developers.cloudflare.com/cloudflare-one/connections/connect-devices/warp/configure-warp/managed-networks/ I've verified that the IP is accessible locally (and also seems to be acessible while WARP is turned on and I'm at the office? I assume it's just considered as a split tunnel exclusion and is routed locally), while not being accessible remotely (since I'm not tunneling this IP through our private network tunnel), and I did see it work one time, but it hasn't worked once since then (without any other changes on my end). 🗒️Note: I've tried both raw ipv4 and DNS for the hostname, ipv4 seems to work more reliably (there's probably some hidden functionality with cf auto-managing split tunnels for managed network ipv4s which doesn't seem to work too well with DNS) 🗒️Note 2: I've also tried both is/in operators for the warp profile config and neither seem to work reliably Any feedback or ideas here would be appreciated, I would very much love to get this to work properly! Thanks for your attention & time 🙏