Yep - this is crazy. If applying the filter fails, the filter is disabled and the target folder is cleared. It happened this morning with about 50 or 60 filters being disabled after the update to 102.3.0 This has happened previously, but did not create such widespread filter carnage before. If the destination folder "cannot be found", there should be the option to have the filter fail on this occasion without changing any of the filter settings. From filter log: Filter action failed: "Move failed" with error code=0x80550009