Remote Browser Isolation busted for weeks

Hi, Anyone else having problems with Remote Browser Isolation? We’re a macOS shop and the tool has been broken for us for weeks. Seems it started applying device posture requirements out of the blue suddenly. We provision access to the service via Access Groups which have device posture requirements configured. That said, all access occurred from devices that met the requirements. This stopped working for 3 weeks and suddenly started working again today inexplicably :frowning: It failed on every browser I tried.

The bigger problem was that no blocks were logged in the access logs for this facility. Support and engineering hasn’t been able to explain why this stopped working after 3 weeks. Waiting for an update on what happened.