Skip to main content


 

Symptoms


A seemingly orphaned escalation was firing off at regular intervals in conjunction with a given workflow
 

Diagnoses


By design escalations are queued in the Server.Async table as soon as a the process containing them is started. Starting the workflow queued our escalation and we saw that it was Type 5 which indicates it was an escalation at the process level i.e. check the start node.
 

Resolution

SYMPTOMS

Remove the escalation from the start of the process.


NOTE

In the Server.Asnyc table the Type column can be anything from 0 to 9 here is what each corresponds to

Empty = 0,
Escalation = 1,
StartActivity = 2,
WakeWorklistItem = 3,
DestQueueProcInst = 4,
ProcessEscalation = 5,
EventEscalation = 6,
WorkListShare = 7,
ProcRights = 8,
RunProcInst = 9




 
Be the first to reply!

Reply