I have an odd situation (or at least so I think) where the primary key between the ID
Vault and a SQL based HR system (read JDBC Driver) can change.

When the interlink key changes I know I need to remove the DirXML-Association and then let
the match policy relink the ID Vault User object to its new match.

I have a policy that properly detects when this happens and removes the association. But,
I can not figure out how to kick the IDM engine to cause an immediate retry. If I manually
make a small change to the ID Vault User object IDM associates correctly with the new key.

Any clues?

Thanks,
Leeland