We have a simple process chain which runs an Open Hub extract.
Our problem is that a couple of times the file has only been partially written, but when we manually retry the process chain a few hours later when we get into office it works OK. Our BASIS colleagues are trying to track down the actual reason why occasionally the ability to write to the output directory gets lost but in the meantime I am trying to look at how we can make the process better to handle this.
Ideally I would like to run the Open Hub DTP, then if this stp fails in the Process chain then for it to automatically retry, but I can't find an option to do this.
Otherwise has anyone done anything smart to deal with situations like this?
I can envisage a solution where I use an event which only is triggered when the OPen Hub DTP fails, and then a separate (Retry) Process Chain which is triggered on this event beign generated. The Retry Process chain simply calling the original failed Process Chain. This would work,. but the problem is I can't control how many retries it would do. We would have to somehow build in a counter for a particular day or such-like.
I was just wondering if anyone out there has an elegant solution (or knowledge of standard functionality I am missing!!!!)