Hi,
I am finding a slightly odd behaviour since upgrading to SAP BODS 4.2.
If a WF fails on Access violation or forcibly closed connection etc. the error is caught in a try catch routine over the whole job and our raise exception kicks in.
We get emailed, lovely stuff and the job when we re-kick it off, recovers from last failure.
This is all great to this point, but if the job fails again later on in the load, we cannot recover.
Looking at logs, we see DFs/WFs have been terminated, but this time it does not state the job has terminated - this is an important point.
This means it cannot recover again from last failure - previous versions this worked fine.
Reason this is quite annoying is due to another post I have put up on Access violations - making this problem also quite common.
At the moment we have to create ad-hoc recovery jobs to manually run from last succesful point onwards and complete the job.
More frustration, be great if anyone is experiencing this and has a fix - I'll attach screenshots etc to illustrate.