IdStory Identity Manager

We are dealing with an interesting thing on one of our projects. We have linked contracts and identities to the same resource. The problem is as follows: If a new record is generated during the synchronization of the identities, then the running job sync will process the contracts for which identities do not yet exist. As a side effect, this sync will have a higher token than identity sync. As a result, this means that you will never create a contracts for these identities without manually changing the token.

We came up with the following solution:
Once contract sync is over, we look into the identity synchronization and copy the value of its token into configuration of contracts sync . Doing so, will ensure that IdM continues to process these contracts again and assign them to identities.

To reflect:
What if someone manually executes contract sync and breaks the token's dependency?
Would it not be advisable to have a mechanism to deal with this as part of the product (and how to solve this problem if the source of identities and contracts is different - including a different token format)?