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

SuccessFactors Email Writeback REST UpdateUserJSON User Update Tasks Fail with 'Null' Error

ReshamDas
Regular Contributor
Regular Contributor

Hi,

We have an earlier working UPDATEUSER solution for SuccessFactors connection failing recently. Following is the code for the UPDATEUSER json parameter in the SuccessFactor_Template REST connection:-

{
"actions": {
"Update Login": {
"call": [
{
"name": "Update Login",
"callOrder": 0,
"connection": "userAuth",
"url": "https://XXX/odata/v2/upsert?$format=json",
"httpMethod": "POST",
"httpParams": "[{\"__metadata\":{\"uri\":\"PerEmail(emailType='6709',personIdExternal='${Integer.valueOf(user.employeeid)}')\"},\"emailType\":\"6709\",\"emailAddress\":\"${user.email}\",\"isPrimary\":true}]",
"httpHeaders": {
"x-http-method": "MERGE",
"Accept": "application/json",
"Authorization": "${access_token}"
},
"httpContentType": "application/json",
"successResponses": {
"statusCode": [
200,
201
]
}
}
]
}
}
}

Deployed initially a month ago, this code was built to write back the value of Email attribute in Saviynt, into the SuccessFactors HR source, whenever the email in Saviynt has been updated for any such SuccessFactors users. A User Update Rule is triggered when email is updated for such user, which creates 'Update User' tasks with Provisioning Metadata value as 'Update Login'. A scheduled WSRETRY job therefore provisions all such tasks, through which the latest email value from Saviynt is written back into SuccessFactors profile of that user.

This process was working absolutely fine until recently, we see that the email writeback is failing, with the generated tasks from email update in Saviynt user profile, remaining in 'Pending' state forever, with no comments or error message written inside. From the logs, we found the following error message appearing on the run of the WSRETRY job:- "ERROR","Error Updating the User from REST - null". PFA the Error_Logs_Saviynt.csv for full logs captured during such job execution.

Also, we tried the email writeback using Postman with the same API details, it worked fine. PFA Postman Working.png for snapshot of the working Postman collection for SuccessFactors email writeback.

Please suggest in this context what could possibly go wrong suddenly that all tasks for this SuccessFactors writeback is failing with above error, and getting stuck in Pending state (PFA Pending Tasks.png).

5 REPLIES 5

rushikeshvartak
All-Star
All-Star
{
"actions": {
"Update Login": {
"call": [
{
"name": "Update Login",
"callOrder": 0,
"connection": "userAuth",
"url": "https://XXX/odata/v2/upsert?$format=json",
"httpMethod": "POST",
"httpParams": "{\"__metadata\":{\"uri\":\"PerEmail(emailType='6709',personIdExternal='${Integer.valueOf(user.employeeid)}')\"},\"emailType\":\"6709\",\"emailAddress\":\"${user.email}\",\"isPrimary\":true}",
"httpHeaders": {
"x-http-method": "MERGE",
"Accept": "application/json",
"Authorization": "${access_token}"
},
"httpContentType": "application/json",
"successResponses": {
"statusCode": [
200,
201
]
}
}
]
}
}
}

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

ReshamDas
Regular Contributor
Regular Contributor

@rushikeshvartak ,

It still failed with same error message with the updated JSON you provided:-

ReshamDas_0-1722863760489.pngReshamDas_1-1722863779499.png

In this context, let me add that Saviynt environment was upgraded on 07/29 from v24.3 to v24.7. We are also getting the pending tasks stuck since similar time. So, is this a bug in v24.7?

Just run job for 1 task from advanced config


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

ReshamDas
Regular Contributor
Regular Contributor

@rushikeshvartak ,

I updated one user VJ020658, and then restricted the Email Provisioning WSRETRY job to pending task key 5286558 for this update.

The job ended up as 'Success', but inside the job log details, it is visible that the task failed:-

ReshamDas_0-1722942005164.png

 

Also, the task 5286558 still remains in Pending Tasks list. PFA the logs captured for this job execution, where only one ERROR message was found as: "ERROR","Error Updating the User from REST - null".

Looks like some upgrade issue with your instance follow support route if this config was working before 


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