after an upgrade from FIM2010 to MIM 2016SP2 (4.6.641.0) I realized that there is a strange issue about sets membership.
There is a simple set filtered by an integer value ( isdisabled=0).
Problem is about membership recalculation when a user change isdisabled value from 1 (exclude from set) to 0 (include in set).
Set is not update till next day (after fim temporal job which also process all set fire at 01:00AM).
This issue is not present for all others set using string attribute as filter even if they are more complex.
This behavior is dangerous because there is an high risk of skip policy because target set is not correctly update.
Following some online post i also rebuild fragmented index but this was useless.
Have you some other ideas (avoid changing filter) ?