Currently, when performing an import for target systems, the correlation value is strictly locked in once the import runs. If a mistake is made during configuration -such as selecting the wrong matching attribute- there is no way to fix it immediately, even though all the necessary data has already been fetched.

For example, I imported a Active Directory system using 'EmployeeID' as the correlation value. After reviewing the generated report, I realized it should have been 'EmployeeNumber'. Although both attributes are fully present and available in the current snapshot, HelloID forces us to wait an entire hour to trigger a completely new import cycle just to change this mapping. The data is already there, but the platform currently does nothing with it once the initial import process completes.

The solution I would like:

We would like the ability to dynamically change or re-evaluate the correlation value for target systems using the data that is already available in the most recent snapshot. If a configuration error occurs, administrators should be able to update the correlation attribute and re-run the correlation logic instantly, without being forced to wait for a full hour to create a new snapshot.