Hi MS team,
I'm developing sync program with cloud filter API. I notice that some antivirus will hook system function (i.e. CreateFile) and trigger fetch callback.
In my scenario, the file was being deleted on server side, and my provider start to delete local placeholder. however, in the deletion process, fetch callback is triggered to hydrate an non-existent file (on server). As a result, I report STATUS_CLOUD_FILE_UNSUCCESSFUL in complete status, but the fetch callback is triggered again to hydrate file.
Here are two question I hope that I can get some help.
1) how to prevent antivirus hydrate file content? should I add some flag when I call CreateFile? or I need some setup for cloud filter sync root?
2) what status code is good for represent that the file is no longer exist and should not retry fetch.