Tasks stuck in the pending queue after reopening from the completed tab.

[ssingh16]

Hi Team,

We observed that when we tried to reopen any discontinued or failed tasks from the completed tasks tab, in the pending tab, tasks showed an "In Progress" status instead of "New." By using the option "Unclaim" in the pending tab, the task's status changes to "New" from "In Progress" and is processed successfully.

But when we tried to reopen the same tasks through the analytics report, in the pending tab, tasks showed a "New" status and were completed successfully.

My question is that when we reopen tasks from the completed tab, they should be in "new status" instead of "In-Progress."

PFA query for wsretry.

Currently using Saviynt version: Saviynt v2020.1

Regards,

Satyam

[Rishi]

HI, we are reviewing and replicating this scenario in our internal environment. We will provide response shortly.

[ssingh16]

Thanks, Rishi We will await your response.

[rushikeshvartak]

Once tasks are in progress (2) then it does not picked up by waretry and considered as disconnected apps tasks

[ssingh16]

Hello Rushikesh,

Thanks for the response!

According to you, these tasks considered as disconnected tasks due to query or something else, but they are actually tasks for the connected application. Do we need to make some changes in the query, or is this an issue that we need to report?

How we can proceed to resolve this issue

Thanks,

 satyam

[nimitdave]

@ssingh16 , the behavior mentioned by you is expected.

1. On manually re-opening a task , it goes to In Progress and is assigned to the endpoint owners if present else admin. Then the current need to unclaim the task , so that it can be claimed by any other user for completing the manual activity that was not done and because of the same reason the the task was brought to pending from completed one. This flow help and helpdesk/manual prov team to work on the assigned backend activities for manual provisioning scenarios. 

2. With analytics , re-open tasks goes to new status, this is done for tasks which need to be picked again for ws-retry job processing.