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

My failed Update User task is marked as Completed

Sampo
Regular Contributor
Regular Contributor

Hi,

I'm using the REST connector to provision Update User tasks to a target system. The problem is that even if the update fails, the provisioning task is always marked as Completed and will not stay in Pending tasks.

The target application always responds with HTTP status code 200 so I'm using the following config to determine if the task was processed successfully:

 

"successResponses": {
"d[0].status": ["OK"]
},
"unsuccessResponses": {
"d[0].status": ["ERROR"]
},

I think Saviynt is able to read the status field from the response because if it fails, I can see the following in application logs:

 

2024-07-05T15:31:21+03:00-ecm-worker-rest.RestProvisioningService-quartzScheduler_Worker-3-jlzw7-DEBUG-successResponses key: d[0].status, value: [OK]
 
2024-07-05T15:31:21+03:00-ecm-worker-rest.RestProvisioningService-quartzScheduler_Worker-3-jlzw7-DEBUG-successResponseText: ERROR
 
2024-07-05T15:31:21+03:00-ecm-worker-rest.RestProvisioningService-quartzScheduler_Worker-3-jlzw7-DEBUG-successResponseValues: [OK]
 
2024-07-05T15:31:21+03:00-ecm-worker-rest.RestProvisioningService-quartzScheduler_Worker-3-jlzw7-DEBUG-unsuccessResponse key: d[0].status, value: [ERROR]
 
2024-07-05T15:31:21+03:00-ecm-worker-rest.RestProvisioningService-quartzScheduler_Worker-3-jlzw7-DEBUG-unsuccessResponseText: ERROR
 
2024-07-05T15:31:21+03:00-ecm-worker-rest.RestProvisioningService-quartzScheduler_Worker-3-jlzw7-DEBUG-unsuccessResponseValues: [ERROR]
 
2024-07-05T15:31:21+03:00-ecm-worker-rest.RestProvisioningService-quartzScheduler_Worker-3-jlzw7-DEBUG-doUpdateUserAction - temp.status - Failed
 
But even though it has temp.status - Failed, soon the following appears in logs:
 
2024-07-05T15:31:21+03:00-ecm-worker-services.ArsTaskService-quartzScheduler_Worker-3-jlzw7-DEBUG-Final status of task 207 - 3
 
and the task is marked as completed.
 
Is there any configuration that affects how many times Saviynt tries to process Update User tasks before they are marked as completed or are they always marked as Completed, even when the task has failed?
 
best regards,
Sampo

 

2 REPLIES 2

rushikeshvartak
All-Star
All-Star

If it fails then it should mark as Error state and moved to completed state.

You can find number of times it tried in arstasks table.

select taskkey,PROVISIONINGTRIES from arstasks


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

Raghu
All-Star
All-Star

@Sampo  it will try until get response from target 20 tries after that it will move completed task sucess /faliure/error  it functionality

you can check under security system level No of tried is defined .

Security system-> Number of tries for provisioning-> it will allow 1-20 triggers only.

Raghu_0-1720208649756.png

 


Thanks,
Raghu
If this reply answered your question, Please Accept As Solution and hit Kudos.