Hello @mochi. What port is this traffic on? Also, just to confirm, the exception you added was an IP based exception? If so, can you also ensure the "Treat like local IP" is checked on the steering configuration?
Sam Shiflett Netskope Solution Architect - North America
I saw that behavior few weeks ago. It should only occur on UDP/443 (quic protocol). The client blocks those UDP/443 flows to avoid the client/app evading the security controls and inspection. Here Chrome should fall back to regular HTTPS TCP/443