I believe $TIMESTAMP$ is the transaction start time (which on large escalations can be off as the transaction grows)
Change over to using $SERVERTIMESTAMP$ (which should be the current date and time from the server) Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of [email protected] Sent: Tuesday, June 07, 2011 9:58 AM To: [email protected] Subject: Escalations - question over create time and timestamps I have an escalation that is almost working fine, but appears to be generating some inconsistent date/time values. Within the escalation, it has a push fields creating an audit record of an sla failure, and putting $timestamp$ in an event date time field. The problem appears to be that the system generated create date, that i would normally assume to be close to the timestamp value, very definitely isn't. We're seeing some large discrepancies. For example : create date 6/6/2011 at 19.23:29 timestamp 6/6/2011 at 19.12:55 any suggestions as to what could be causing such a large discrepancy in what should be identical values?
