Hello,
We observed the following behavior with an internal population synchronized via a CSV import configured in RECONCILIATION mode.
When an internal employee reaches their leaving date, the identity is disabled in Memority. However, the user may remain present in the CSV file for several days or even weeks after their departure.
Later, when the user is finally removed from the CSV file and a new import is executed, the system updates the deactivation date again — even though the identity was already disabled earlier.
This behavior may impact archiving and deletion timelines, since these processes depend on the deactivation date.
Is this expected behavior?