The ProvisioningJob (WSRETRYJOB) does not take pending tasks.

[Amine_MERZOUK10]

Hello team,

I am encountering a problem on the environments, it's about job "ProvisioningJob (WSRETRYJPB)" which launches successfully .

Although the provisioning job is operational, there are still pending tasks that have not been completed as planned.

I am sending you the captures of the different configurations, and would be happy to receive your answers.

Example ( I have the following jobs today "280748" and "280747", I run an analysis in the data to check if my job should be completed by the next provisioning and I get a zero as a result.

[This message has been edited by moderator to mask usernames from image]

[pmahalle]

Hi @Amine_MERZOUK10 ,

I can see task create date is today's date and you used condition at.startdate < sysdate(). Use at.startdate <= sysdate() and check

Let me know if it works.

[Amine_MERZOUK10]

Hello @pmahalle ,

I made the requested change but I still scored zero.

[armaanzahir]

I'm not sure if the query you're using in the data analyser is correct. The query has two conditions on the same column (taskkey) separated by and operator comprising a different value check. 

Since taskkey is unique to an entry in the table, not even a single record from the arstasks table will have taskkey  = 280747 and taskkey = 280748. It can either have 280747 or it can have 280748

[Amine_MERZOUK10]

Hello @armaanzahir ,
Thanks for your message,

I deleted an ET and I executed the request, I see that the result is 1 . The purpose of the request is to check if my task needs to be completed by the next provisioning.

( it finds the identifier of my task, so supposed to finish the next job but it finds my concern, the task is still waiting).

Best regards,

Amine M

[pmahalle]

Hi @Amine_MERZOUK10 ,

Did you check in the logs, Wsretry picking up the task or not? Can you share the logs.

[rushikeshvartak]

Remove Advance Query and try

[Amine_MERZOUK10]

Hello @pmahalle,

I attach a copy of the log a whole day .

Hi @rushikeshvartak  I deleted the advanced query in the job settings and I relaunched the job and I have no result ( the jobs are still pending). 

Best Regards,

Amine MERZOUK

[pmahalle]

Hi @Amine_MERZOUK10 ,

In the logs I can see "xxxxxx present in ARSTASKS_EXEC , do not add to processing list". From the logs seems like some other WSRETRY job instance already picked up the tasks and not allowing to other WSRETRY job.

Is there any other WSRETRY provisioning job already in running state and stuck? If yes, can you kill that by server restart and try again. You can restart the server to kill the job from UI, Admin --> Admin Functions --> Application Restart

Let me know if it helps.