Thanks for reporting this; this will be raised during our regular policy performance review as part of our normal Engineering cycle. We monitor the performance of our deployed policies and adjust them as needed whenever a change like this happens. I'll let you know once the new policy has been deployed to SwiftSense