There is no rough guideline that takes parameters x and y then yields parameter z. You have to consider what the escalation is doing and how quickly it needs to do it. If you have an SLA that needs to fire 2 hours after a ticket is created, you do not want that escalation to fire every 2 hours. You want to give the people involved with the SLA the longest lead time possible to address the issue. If you have a batch cycle that loads a data feed every 24 hours and the data source is refreshed every 24 hours, you want the escalation to process the fresh data as soon as it becomes available and no more.
Axton Grams On Thu, Sep 25, 2008 at 9:44 AM, Brittain, Mark <[EMAIL PROTECTED]> wrote: > Hi All, > > I have some escalations running but I think the time interval is > excessive. Here are some simplified examples. > > Last modified more than 20 minutes ago - time interval is 11 minutes > Last modified more than 1 hour ago - time interval is 30 minutes > Last modified more than 2 hours ago - time interval is 30 minutes > > Any suggestions, greatly appreciated > > Thanks > Mark > > > This e-mail is the property of NaviSite, Inc. It is intended only > for the person or entity to which it is addressed and may contain > information that is privileged, confidential, or otherwise protected > from disclosure. Distribution or copying of this e-mail, or the > information contained herein, to anyone other than the intended > recipient is prohibited. > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
