First check the following items.
1. Check the Agent overview and verify the agent configuration matches the configuration that has the filter applied.
2. Verify that the agent configuration has been applied to the agent group and is updated.
3. Make sure the agent has an update configruation by checking the time / date stamp on the cg.ead file on the client or looking at the last update time in the Agent overview in enforce.
If the issue persists then check the format of the filter. A valid http(s) filter for web sites looks something like: (note the following is not valid for Sharepoint shares / Cloud storage)
-*test.com
While that filter will prevent incidents from generating http(s) incidents to the test.com web site it will not work for cloud sync applications.
As per the Administrator guide under Cloud Storage settings the filter must have an astrerisk after the filter entry. To properly filter sharepoint / cloud storage saves to test.com the filter entry must look like:
-*test.com*
After applying the above syntax to the agent configuration filter the agent will no longer generate incidents when saving to the share. See the admin guide for more details.
Thanks for your feedback. Let us know if you have additional comments below. (requires login)