You are viewing limited content. For full access, please sign in.

Question

Question

BUG: Interrupted task not interrupting its timer

asked on October 8 Show version history

I am designing a new process and running into an issue. At least, I think it's a bug. Basically, I have some automation in place that should complete a process once a verification has been received. I'll check this daily via lookup activity in Workflow. Note that this is v12; hopefully it has already been found and addressed for the upcoming release.

From my simple testing workflow below, you can see that there is a user task with a timer event that will call the workflow periodically. If confirmation has not been received yet, just end that branch and continue to wait (left path). However, if confirmation was received, proceed to other tasks starting with throwing a signal to interrupt the waiting task (right path).

The logic all works as I intend except for one major issue: the Timer event remains active. I believe this is a bug since the underlying task was interrupted; there is no reason for the timer to remain active. In fact, the timer stops repeating so it's not really doing anything. BUT, the workflow still shows as in progress--after completing the final task--since the timer is still active. And since it's not actively repeating, my guess is it will never hit the repeat limit to even time out on its own (not that that would make it better, just something else worth noting).

 

0 0

Replies

replied on October 8

This sounds like the same issue reported here:  https://answers.laserfiche.com/questions/231782/interrupted-task-still-has-active-timer-catch-event#231794

This has been a little annoying - I have a half dozen or so every day that have everything complete except for a single Timer Catch event that I have to manually interrupt to fully end the instance.

1 0
replied on October 8

Yep, that sounds the same. I really did search for this before posting.

0 0
replied on October 8

The good news is they don't seem to ever trigger after the completed task or cause any issues later in the process (at least that I've seen), it's just this one hanging thread that is being ignored by the system.

The easiest way I've found to identify them is when you eventually end up with a complete instance that doesn't actually show complete, it just doesn't have any tasks or activities running.  Then you can manually interrupt the one hanging timer which promptly ends the instance.

0 0
replied two days ago Show version history

I ran into the same problem as well in 12, but I did not have this setup in 11 so I'm not sure if it worked differently there. I would think the signal catch could/should override the timer.   

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.