Engineering change notice flow stuck

[SC_8321054]

Hello,

I have created and submitted a new change notice. but it seems to be stucked because the reviewer and auditor did not get the notification to complete the task. I checked again the roles, and everything is fine.

please help anyone...!

Thanks,

Sandeep C.

[HelesicPetr]

Hi @SC_8321054 

It would be nice to send a screenshots of workflow table from change task and change notice.

Check the process tab of the change notice 

also check the workflow process

PetrH

[SC_8321054 · Accepted solution]

Hi Petr,

When I opened the process manager, I saw an error.

You may not "Set Life Cycle State " xx part, Y.2 (Design) because it is checked out"

I have checked in the part now, and resumed the process. now it moved forward.

you are great 😀 thanks.

[avillanueva]

There are a couple of things assuming system has been working and no changes to process recently. The Change Notice workflow and Change Task workflow trigger each other to move via a sync robot. The robot is typically triggered by a state change on the other object. If the change notice moved to Implementation for example, the change task would start moving. Sometimes it failed to process the state change event and misses it. Never was sure why this occurs but once missed, it can hang there. I've created some check reports to spot them. Following Peter's advice, use the Process Manager to see where the green box is. If its a sync robot and it should have fired, you can manually complete it.  This is rare but can occur from time to time. 

If there is a failure in the code, look in the QueueManager for a failed WTPropogation or WTUserWork Queue entry. You can try to resume it but some bit of code threw an exception.

Another can I am dealing with is a bit larger. I've seen my entire background method server get hung up and nothing moves. All queue entries show ready. My recourse has been to restart the process and things start moving normally after that. I suspect some DB issue but investigate. Its not likely this, just noting.