OK, so interestingly enough, I have another forum ticket logged specifically for the issue with #_ACTIVITY_RESULT# causing errors when the action is actually successful, which keeps me from being able to set up sort of a "retry" through a loop action or an if action. This is actually the route I was trying to go to create this retry type of feature.
So whether the issue on that can be answered on this forum thread or not, I really wanted to discuss the enhancement ability to create a number of retries like other ftp softwares allow you to do. This way, it's much more up to date and can handle failed connection requests a set number of times.
But to discuss #_ACTIVITY_RESULT# a bit further, basically say you want to set up an if activity and say based on the #_ACTIVITY_RESULT# variable, which tells you the "failure" message, then rerun do another set of actions, else if it does not fail do another set of actions. That's where my problem is. When the activity before is successful, the #_ACTIVITY_RESULT# variable is essentially blank. This becomes a problem when feeding that variable into an if action because, like mentioned in the other forum post, TDP says that the variable used cannot empty ("Expression can't be empty is the error it brings back.") So I'm really stuck at this issue trying to create my own retry procedure from a TDP automation.
Let me know if you need anything else from me.
Thanks!