Share all details about your problem, including any error messages you may have received.
Hello,
Recently I noticed the name of the task results of Identity Refresh changed from containing the increment number to some ID, just like in the following image:
@bruno-co there is no change in process , i can see now sailpoint still adding the display name first then appending 1,2, 3–
So for this identity may be whatever id is display name , that means this identity is not correlated one and create target aggregation.
I managed to fix the issue by renaming the last Refresh Identity Cube Task Result. I manually introduced the next increment in the TaskResult name and subsequent executions of the task are now automatically incrementing the number.
I still can’t figure out why it stopped incrementing and started putting in that random number. Is there any justification for that?
Hi @bruno-co glad to hear that you resolved it…
TBH I don’t know why this happened but I can think loudly with you :).
The Last Incremental Task Result Was Missing or Deleted
IdentityIQ relies on the last stored TaskResult name to determine the next increment. If the last Task Result was deleted, renamed, or corrupted, IIQ couldn’t find the next number and switched to a UUID format as a fallback. When you manually reintroduced the numbering, IIQ picked it up again and resumed its normal behaviour.
The TaskResult Table in the Database Was Reset or Cleaned Up
If the spt_taskresult table (where IIQ stores task results) had a cleanup or database maintenance, it could have removed older task results, breaking the numbering sequence. Left IIQ unable to determine the last increment, causing it to generate unique IDs instead.
A System Restart or Cache Flush Might Have Triggered It
If IIQ was restarted or the cache was flushed, the in-memory task execution tracking may have been lost. After a restart, if IIQ couldn’t find a valid last task result, it defaulted to using a UUID instead of a number.
The Task Definition Was Accidentally Modified
Even if no configuration changes were intentionally made, sometimes editing and saving a task definition (without actually changing settings) can reset naming conventions. If the Task Definition ID was regenerated, it could have reset the TaskResult name.
Again I’m not sure about anything of that just thinking loudly with you :).