Afternoon All,
We've come across a bit of an issue since moving from RP3 to RP6 at the weekend. We've got a few request workflows that start/stop the clock at various points throughout the process. These tasks seem to stop and start the clock when required (the service window shows the clock as stopped, as do the entries in the SLM screen), but when the clock is restarted, the escalation and breach times don't seem to be recalculated at all and so they occur based on the time the clock was first started at request submission.
Anyone else come across this? I can't see anything in the KB that matches this behaviour.
Cheers,
Dan