Dwayne, Just a few guesses... ( It is very hard to tell without seeing all of the logs.)
Well.. it actually could have something to do with it. What if... the ARS server is holding on to the old results of this SQL: SELECT C536870931 [the field getting updated] FROM T580 WHERE C1 = 'PIQ00083' And using it from the first time around rather than the second time? Basically if the select is done to return the whole blob, and then the whole blob is re-written every time, then if the first copy of the blob is used during the second trip through the workflow the final data would look like the first pass through the workflow never happened. However that would be a real bug that BMC would have to fix. Another possibility might be that you have a filter phasing issue where the second push is not seeing the changes from the first push. (Assuming your updating a record in your "diary" form.) If that is the case try to set the filter that is doing the push to be non-phased and see if that fixes the issue. -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On 9/12/07, Dwayne Martin <[EMAIL PROTECTED]> wrote: > I figured out why the filter is firing twice. We have a bug in our system > that causes emails to be sent in duplicates or sometimes in triplicates. I > knew it was happening in our live system but didn't realize it was happening > in our test system till now. > > An event triggers an email, which spawns two AR System Email Messages entries > instead of one. Each one of them pushes a value to the other form, which is > why the workflow happens twice. > > Unfortunately, this has nothing to do with why the pushed values aren't > showing up. > > Dwayne Martin _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
