Subjob throws error but still triggers OnSubJobOk

[Anonymous]

I am trying to purposefully trigger the error handling I set up. I first attempted this by trying to pull in values that are greater than the length specified in the schema. The job throws the error "Data truncation: Data too long for column 'Title' at row 1" as expected but then the job triggers the OnSubjobOk path instead of OnSubjobError. 

Why is this happening? How can I intentionally trigger the OnSubjobError functions?

[Anonymous · Accepted solution]

Just had to enable "Die on Error" on all DBOutput components in the subjob. Subjob is now failing as expected.