PIR Change task created 20 hours late after closing the implementation task for a change request

[kkswamy]

Hi,

We have a workflow with business rule that,

Whenever change implementation task gets closed then if the change request "close code" is "successful with issues" then post implementation task(PIR) should create and assign to our CAB. But for one particular change request, the PIR task created after 20 hours,

why this huge delay in the creation of the change task?

Note:In our workflow, we don't have any wait for condition or timer activities for this.

Any help much appreciated.

Regards,

KK Swamy.

[kkswamy · Accepted solution]

I found the root cause for this issue,

It is because we have a business rule, and the condition to trigger the business rule is "if state changes to "closed" then only business rule will execute.

as per our process if the user clicks on "save" or "update" buttons other than "close" button on the change, change request state will not change to "closed", until someone clicks on the "close" button PIR change task will not create.

[zishan khan]

Hi @kkswamy , can you please help me how I can develop a solution as when change task is closed with close code as : Unsuccessful or Success with issues, then PIR task should automatically get triggered for such tickets since they are not implemented successfully and get assigned to the implementing team.