You could check the child return code returned by tRunJob in an if trigger. Check out the Outline view of the job. Here you can see what components have available as return values.
OnComponentError will only be used if the component fails. It is a error handling. You can do a bit tricky design and let after OnComponentError follow your normal job flow but the actual design idea behind that is to simply do some cleanings and let the job stop at this point. To check the child-return-code is not a workaround, it is a clean approach to react after a child job has returned something different than null or zero as return code. We do sometimes such things e.g. the child job detects some missing data bit this is actually not a fault, it could be a matter of timing. In such cases we send a exit code different from zero. An in the parent job we receive this information and let follow a appropriated workflow.
