If an initial synchronization ignores an object because it finds processes still running in the Job Queue, then a subsequent synchronization will also not capture this object because it is excluded by the revision filtering, under certain circumstances:
Circumstances are all those where the changed object is not commissioned out at all or if it is a change to an account of the Person record, but the Person record (Employee) should be synchronized as well.
This is a product defect (35049).
WORKAROUND
None
STATUS
This will be fixed in a future release of the product. If you require this immediately corrected, please contact Support for a hotfix referencing the defect ID 35049.
© 2025 One Identity LLC. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center