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).