starneld

Setting the update policy to N-2 (or any other configuration) would not have avoided the issue. The Falcon sensor itself wasn’t updated, which is what the update policy controls. As it turns out, you cannot control the content channel updates - you simply always get the updates.

I’ve read that it turned out to be a nothing burger primarily because there was a concerted effort to address the problem. That said, yeah, nothing melted down so functionally there was no issue.