Saviynt unveils its cutting-edge Intelligence Suite products to revolutionize Identity Security!
Click HERE to see how Saviynt Intelligence is transforming the industry.
Saviynt Copilot Icon

ServiceNow Provisioning Failing intermittently

dchaudhary1
New Contributor III
New Contributor III

Hi All,

We are facing this issue when we are trying to provision serviceNow account. The provisioning fails intermittently with following error:

"message":{"error":{"message":"Operation Failed","detail":"Error during insert of sys_user (${user.firstname} ${user.lastname})"},"status":"failure"},"statusCode":403,"description":null,"status":"Failed"}}

This error is observed if user already exist in ServiceNow, but this is not the case. We have verified that user we are trying to provision is not present in serviceNow.

Following is the createAccount Json:

{
"accountIdPath":"call1.message.result.sys_id.value",
"responseColsToPropsMap":{

},
"call":[
{
"name":"call1",
"connection":"userAuth",
"url":"https://XXXXX-service-now.com/api/now/table/sys_user ",
"httpMethod":"POST",
"httpParams":"{\"active\":\"${user.status}\",\"company\":\"${user.companyname}\",\"department\": \"${user.customproperty5}\",\"email\":\"${user.email}\",\"employee_number\":\"${user.employeeid}\",\"first_name\":\"${user.firstname}\",\"last_name\":\"${user.lastname}\",\"location\":\"${user.location}\",\"manager\":\"${user.manager}\",\"mobile_phone\":\"${user.phonenumber}\",\"phone\":\"${user.customproperty12}\",\"title\":\"${user.jobcodedesc}\",\"user_name\":\"${user.username}\",\"u_branch\":\"${user.customproperty7}\",\"u_directorate\":\"${user.departmentname}\",\"u_join_date\":\"${user.start_date}\",\"u_person_category\":\"${user.customproperty22}\",\"u_person_category_code\":\"${user.customproperty21}\",\"u_position_number\":\"${user.jobCode}\",\"u_reports_to\":\"${user.manager}\",\"u_request_approver\":\"${user.customproperty20}\",\"u_responsibility_centre\":\"${user.costcenter}\",\"u_section\":\"${user.customproperty10}\",\"u_sub_section\":\"${user.customproperty13}\",\"u_termination_date\":\"${user.termDate}\"}",
"httpHeaders":{
"Authorization":"${access_token}" },
"httpContentType":"application/json",
"unsuccessResponses":{
"error.message":"Operation Failed" }
}
]

There is no error in log other than 403. Also when tried this api separately on postman , it is working as expected.

Any pointer will be appreciated !!!

Thanks

[This message has been edited by moderator to disable URL]

8 REPLIES 8

SumathiSomala
All-Star
All-Star

@dchaudhary1 JSON is looking good.

Did you observe any specific case it is failing to create new account?

Could you please check the user status and manager attribute for the failed scenario.

You can also use

\"active\":\"true\"

 

 

Regards,
Sumathi Somala

If this reply answered your question, please Accept As Solution and give Kudos.

Hi @SumathiSomala ,

Thank you for the reply

I have same manager and active is true , out of three one works and two fails.

Thanks,

Divya

@dchaudhary1 what it mean by out of three one works and two fails?

Regards,
Sumathi Somala

If this reply answered your question, please Accept As Solution and give Kudos.

@SumathiSomala ,one user got provisioned and other two failed provisioning. That's what I have mentioned in my query the provisioning works intermittently.

 

rushikeshvartak
All-Star
All-Star

Its should be data issue. does any of data contains special characters


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

Hi @rushikeshvartak ,

Thank you for your reply.

I even tried same data for each user only username is different , still no luck.

Also when I try directly to on postman , it is working for consecutive users.

Thanks,

Divya

This generally happens when the attribute mapped for provisioning is not correct.

Also check the username you are trying to provision.

Regards
Manish Kumar
If the response answered your query, please Accept As Solution and Kudos
.

dchaudhary1
New Contributor III
New Contributor III

Thanks @SumathiSomala , @rushikeshvartak .

I got it working as one of the field "start date" was not passed with right saviynt attribute , hence it would provision user with username ${username} and it will fail subsequent users as the user with ${username} existed.