User Update rules running for deleted account

[Caesrob]

Hi,

We have a user update rule configured like this:

When a user is converted back to Active through the import, sometimes some of these attributes will have updated. Since they're updated, an updateAccount task will be created. With this also comes a newAccount task through a technical rule. Saviynt's workflow (from documentation) says new Account tasks should be provisioned before updateAccount tasks. We think this does not always work correctly, especially if a lot of inactive users are set to Active in the same import.

We think this because when multiple of our users were set back to Active, we noticed the updateAccount tasks were being provisioned for their deleted accounts and not their new accounts which obviously gives an error:

Also, we can see here that the updateAccount task was created on Oct 01, 2024 12:52:25. If we look at the newAccount task, we can see that it is completed on Oct 01, 2024 12:22:36. So there should be no way that the updateAccount task is being executed for the already deleted OpenLDAP account the user had before:

Is there any way to disable user update rules/technical rules to run for deleted accounts?

[NM]

@Caesrob was the update account task created before account deletion?

[Caesrob]

Hi,

No, the account was deleted on February 2024 and the updateAccount task was made 2 days ago.

[NM]

@Caesrob seems a bug .. it shouldn't create an update account task for suspended account.

[NM]

@Caesrob as per current process of yours .. there is a seperate rule which will trigger new account creation when user is rehired and if any of the value is achanged a update account task is triggered as well?

You can add a not update condition on status as well.