Thats bizzare. I have not seen this one before. There are no error in the k2 log nor the Windows event log?
I have never encountered this either. In K2 Service Manager, have you tried doing a "Goto Activity" back to this same activity to have it re-run? It'd be interesting to hear what happened.
The portion of the workflow shown is a very small part - there are about 75 activities in the workflow. One of them is an Infopath activity hanging off the start box in parallel to the main workflow that is assigned to the K2 Service Account. The purpose of this activity is to give us a way to fix problems by exposing the entire schema for modification, or in this type of instance to be able to execute a gotoactivity to get it restarted. If this activity is used to modify the schema, it will restart itself.
Had this activity not been there, these 3 workflows would have stopped and K2 would consider them completed. If I use the goto I no longer have the 'maintenance' step available for attempted fixes. This will be my last resort. I have opened a problem ticket and I'll see where that takes me before using the 'goto' on these.
Thanks for your input.
Keep us updated.
Totally off-topic, but regarding the issue with Goto:- having the ability to Goto (and terminate existing active activities is good to have) - serves as a solution for a few use cases I've seen in the past, but extending this ability would be excellent, i.e.:
- Goto a single activity and terminate current active activities (only
- Goto a single activity and terminate only the calling activity
- Goto multiple activities (that would be really handy!)
Various situations crop up where this functionality would be a real benefit, i.e. when doing state migration from legacy systems.
Regards
Gabriel
I analyzed the K2 Log and found these entries for this processinstance at that specific time (edited for brevity):
"ExecLine","ProcessInstance::ExecLine","5100 Executing Line Rule Quality Approval to SFR(431), StartAct:Quality Approval(404), Proc:MOC(1608)","",""
"ExecutedItem","ProcessInstance::ExecLine","5170 Executed Proc:MOC(1608), Item:Quality Approval to SFR.LineRule, Status:True","",""
"ExecutedItem","ProcessInstance::ExecPrecRule","5170 Executed Proc:MOC(1608), Item:Approvals Reviews (SFR).PrecRule, Status:True","",""
"ExecutedItem","ProcessInstance::ExecStartRule","5170 Executed Proc:MOC(1608), Item:Approvals Reviews (SFR).StartRule, Status:Completed","",""
"ExecutedItem","ProcessInstance::ExecDestRule","5170 Executed Proc:MOC(1608), Item:Approvals Reviews (SFR).DestRule, Status:Completed","",""
"DestRuleAddUser","ProcessInstance::ExecDestRule","5180 Adding User u859272 to Dest Rule for Act:Approvals Reviews (SFR)(432), Proc:MOC(1608)","",""
"ExecClientEvent","ProcessInstance::ExecClientEvent","5040 Executing Client Event Review Notification(453), Act:Approvals Reviews (SFR)(432), Proc:MOC(1608)","",""
"ExecCodeItem","ProcessInstance::ExecuteCode","5010 Executing Code Item ClientEvent - Review Notification","",""
"ExecutedItem","ProcessInstance::ExecServerEvent","5170 Executed Proc:MOC(1608), Item:Review Notification.ClientEvent, Status:Active","",""
These last 3 lines seem to indicate that the Client Notification event was run and is active, but I can't find the XML file in the Shared Documents folder. No response yet on the support ticket.
