Provisioning Task stays in Pending Tasks list even though it worked

[TimoR]

This topic is about using the ENABLEACCOUNTJSON for Active Directory.

The content of the ENABLEACCOUNTJSON is currently as follows:

{
"USEDNFROMACCOUNT": "NO",
"DISABLEACCOUNTCHECKRULE": [
"CN=${user.systemUserName},OU=Users 2,[...]"
],
"AFTERMOVEACTIONS": {
"userAccountControl": "512"
},
"REMOVEGROUPS": "NO",
"RESETPASSWORD": "YES"
}

(Parts of the DISABLEACCOUNTCHECKRULE have been shortened with [...] for privacy reasons.)

When we run the provisioning job, the respective account gets enabled successfully in Active Directory, but the task stays in the pending task list and does not get moved into the completed tasks list.

In the provisioning comments, it says the following:

Checking DN for CN=K_123527,OU=Users 2,[...]. FOund an inactive account -CN=K_123527,OU=Users 2,[...] and the attributes-[:] match. This account will be enabled 

So it should be fine, right?

Can anyone help me determine why this task does not get completed, even though what should be done has been done?

Thanks

[rushikeshvartak]

It should be issue in overall json

[TimoR · Accepted solution]

I found the problem myself, I was missing the following line, after putting this in, it worked as expected:

"MOVEDN": "NO",