Thanks Phoneboy. We created a chained exclusion for example of Box.exe, as well as a number of other Box processes that we found running. We used the format like so below:
![Screenshot 2024-04-18 144022.jpg Screenshot 2024-04-18 144022.jpg](https://community.checkpoint.com/t5/image/serverpage/image-id/25336i814D9108090DA28F/image-size/large?v=v2&px=999)
We also tried making one that was wildcarded into the path. We don't get any logs indicating things are being blocked, so we're not sure what other process we might need. I presume this wildcard makes it recursive, but not sure.
![image.png image.png](https://community.checkpoint.com/t5/image/serverpage/image-id/25337iBF74E6F72792F0BE/image-size/large?v=v2&px=999)
OneDrive we also tested and it initially seemed to be working fine, then eventually generated an error. However, the files were all still accessible so that's acceptable as a fallback plan.