When properties for vApp sharing are changed(adding/removing users and/or changing their level of access), the vApp Modification blocking task is not triggered.
Furthermore, if the blocking task is triggered due to other triggers (a name change, for example), it appears that the permission changes already occur before the blocking task kicks off. I believe this is the case due to the fact that the permissions displayed in the vApp object in the blocking task include the changes(while the blocking task is still blocking!), whereas the other information (lease time, name, description), are all holding old values.
Am I doing something wrong?