Pending task is not getting completed even after running wsretryjob

[RajeshA]

We are seeing one of the Azure AD Add access task  (task id: 434634 )not getting completed. PFA the logs, Can you explain what this below log line tells us. Log is saying it is not getting involved in processing list. Can you please guide us on this issue. Because of below line task is not getting processed

As you see the task is with status as New and with no provisioning comments.

Below is the provisioning job trigger which shows no filter is being placed on task level etc,

Automated provisioning is enabled for that endpoint and below is the only provisioning threshold we have set

[pmahalle]

Hi @RajeshA ,

Make sure Provisioning connection is present in the Security System.

[RajeshA]

It is present Pmhalle. Can you let me know what this line tells me. what is arstasks_exec and Why is it not adding to processing list

[pmahalle]

Hi @RajeshA, 

Can you share the screenshot of whole security system.

[RajeshA]

PFB

[pmahalle]

Hi @RajeshA ,

Security System configuration looks good, just try by enabling the Persistent Data option.

Also, Issue is only with one task you mentioned or for all tasks related to azure ad security system?

Is there any Wsretry/provisioning job stuck in running?

[dgandhi]

Try to run the provisioning job just for this specific task and see what is the result.

[RajeshA]

Hello @dgandhi  As this is issue is in PROD environment we don't have that flexibility to configure/test. Can you let me know why do you want me try that. Do you find out something in logs or screesnhot that is related to wsretry trigger that causing this issue

[rushikeshvartak · Accepted solution]

Share output of below query

select * from arstasks_exec

[RajeshA]

PFA the zip file which contains arstasks_exec, the task id that is not getting completed is under job id 5579631. I also attached the job id related record from ecmimportjob table.

I see this job id related job (which runs every 12 mins) in running jobs still executing. However if you see the last run it is getting updated.

I also attached our server logs which shows the task is still not getting picked up and coming like below

[rushikeshvartak · Accepted solution]

Since Task 434634 is picked by another job new job is ignoring it. 

Run Provisioning Job individually for Task 434634.

Does WSRETRY Jobs are conflicting ?

[pmahalle · Accepted solution]

Hi @RajeshA ,

As I asked above, is there any Wsretry/provisioning job stuck in running? Seems like task id: 434634 is picked by another job?

If there is provisioning job in stuck state, kill it by server restart and then check.

[RajeshA]

After performing the restart of the system this got resolved. 

Thank you @pmahalle , @rushikeshvartak @dgandhi  for your assistance on this discussion.

[Amine_MERZOUK10]

Hello @RajeshA @pmahalle @rushikeshvartak @dgandhi ,

I meet the same prologue currently, what do you hear with the system reboot ( what are the orders to be made please) ?

Can you direct me ? Thank you for your response

[RajeshA]

@Amine_MERZOUK10  If you also facing same issue like what I had here, where tasks are not getting processed. Check if there is any struck provisioning job which already picked up that task. Since that struck job already have that task picked up (you can get that by looking at output of select * from arstasks_exec) subsequest provisioning jobs will not pick up that task to complete.

Now to clear the struck job, you need to restart saviynt. You can do it on your own or raised FD ticket based on version you are on.