The question I would ask is 'why was it not 'working' before'....I sometimes come across stuff that stops working properly after an upgrade, just to find that we were using something incorrectly and the 'thing' was fixed by the upgrade to work properly, so I need to adjust my workflow to actually do what was designed....but I've never experienced this with a 'no touch' situation..
On Wed, Dec 3, 2014 at 9:35 AM, ddussie <[email protected]> wrote: > That is correct. > > This business time is adding 1 minute (so technically timestamp could have > been used), this time is being used by the escalation that runs every 4 > mins, that then sets that time field to null. I will change to Business > time2 or timestamp. > > Agree also, this loop was not being closed; which i have rewritten and is > now closed. > > But why all of a sudden this is working as written (looping) which is > incorrect but working. > > This is happen sporadically with other filters in the environment, so a > things go berserk, I rewrite. > > > > -- > View this message in context: > http://ars-action-request-system.1.n7.nabble.com/Filters-actions-are-firing-wierd-or-correctly-tp119984p119989.html > Sent from the ARS (Action Request System) mailing list archive at > Nabble.com. > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
