I'm creating a Job to run as a scheduled task and it involves many things, like reading/writing to databases, and Moving files to a file server.
My problem is that I'm trying to make the job error resistant. Like if the connection to file server down, then simply log the error and continue to process other stuff.
However, every time I get a error, the job keeps dying. I can catch the error using tAssetCatcher or tLogCatcher but it doesn't stop the job from dying.
some components have "Die on Error" check-box, some - not
also this checkbox not help with Null-pointer errors
most "error-proof" method - split Job for separate independent sub-jobs, and run them from parent Job, where You can manage logic based on SubJob result
