That's the thing. I'm trying to create a "retry" type of feature, so I actually do have to have the stop on error unchecked so it can continue if there is an error. The problem is purely the success. I have to be able to evaluate the success to proceed at all with any type of if or looping activity. A good example is the log command. if I just log the #_Activity_Result# after the fact, it will actually show "nothing" or the error depending on the error of the previous action. That's absolutely exactly what I need other actions to do. Therefore, say you try an if action and say to evaluate the #_Activity_Result# and if there is any type of error that comes back, do something. Even doing this and not even specifying on the "else" part anything, it will work ONLY if there is an error. If there is success, it cannot evaluate this variable on success to even look for the failure message and errors out immediately. I need it essentially not to error and allow the if action or the looping action to evaluate even if there is no error or nothing that came back in #Activity_Result#. Unchecking the stop on error at this point would just send it on past the if action and go to something else and I need it actually to decide which way to go on the if action. I know its hard to explain but I really just need to actually have it not error on the evaluation of the variable in the if/looping actions similar to how it does in the log action.
Thanks!