Skip to main content
Nintex Community Menu Bar

Activity shown as Active but no worklist item

  • December 18, 2007
  • 5 replies
  • 23 views
Forum|alt.badge.img+8

I've got 3 process instances that have stopped at the same place (1500 others are OK). Using the K2 reports page it shows the activity as being active with the proper destination user. However, the user didn't receive an email notification (infopath client event), doesn't have a task in his K2 Tasklist, and when I check it using Server Manager there is no worklist item for that activity.


I've added a jpg attachment that is actually two images in one. The top one shows a partial K2 report view of the activities so far, and the other is a snip of the viewflow diagram for this part of the workflow. There is also more text describing the workflow.


So:



  • The destination rule has executed and assigned the correct user.
  • There is no start rule
  • The activity was instantiated.
  • The  Infopath Client event (first event of activity) creates the Infopath XML file for the activity and sends an email to the user. This has not occurred

Why didn't the event fire? What can I do to get this corrected?


14598i260BE58195FABC06.jpg

    5 replies

    Nintex Partner
    Forum|alt.badge.img+10
    • chrisgNintex Partner
    • Nintex Partner
    • December 19, 2007

    Thats bizzare.  I have not seen this one before.  There are no error in the k2 log nor the Windows event log?


     


     

    Nintex Partner
    Forum|alt.badge.img+9
    • BobNintex Partner
    • Nintex Partner
    • December 19, 2007
    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.
    Forum|alt.badge.img+8
    • SteveJones
    • Author
    • December 19, 2007

    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.

    Forum|alt.badge.img+4

    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

    Forum|alt.badge.img+8
    • SteveJones
    • Author
    • December 19, 2007

    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.


     

    Sidebar Buttons
    Nintex Community Home Contact Nintex Support Email Nintex Community Check Nintex Status
    Terms & ConditionsAccessibility statement