To Preface: 

We use two different task status’: one to represent that the task is completed and the request is completed. Another to represent that there is still work to be done on the request, so the task gets “rescheduled,” and a new “follow up” task gets created. The Request remains Open until the last task is completed. The work on the rescheduled task is essentially completed. 

Currently we have a time clock BR that does a perform time clock event generation when the task status changes. Also, side note: there is a value BR (before update) that will change the Completed task status to Reschedule if it needs to be rescheduled.

It appears that the time clock rule can only evaluate one Stop Action. 

Question 1: Does the time clock rule only evaluate and use the first Stop Action even if the value that we define doesn’t match the task status?

Please see pics 1 & 2 below to see the result of a Rescheduled Task. Fortunately the total labor time is calculated and still gets created even though the time clock event doesn’t match.

Pic 1: One attempt to get the time clock event to show either Completed or Rescheduled and calculate Total Labor Time (Actual Labor):

Pic 2: The result when the sibling task gets rescheduled. Again the work is essentially done on this task and a new one is created. We are hoping the time clock event will show Rescheduled, but it doesn’t. 
 

Question 2: Is there another way to set up time clock(s) to achieve showing the correct time clock event? I don’t suppose I can split Actual Labor into two rules? 

I’ve also attempted to separate the calculation of total labor time into two, but I don’t think this works as it doesn’t know which Start to use if it is on two different clocks, regardless of sequence.