Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Save $650 on Qlik Connect, Dec 1 - 7, our lowest price of the year. Register with code CYBERWEEK: Register
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Errors & Exception not being captured

Hi

Can anyone help with an issue I'm having with tLogCatcher and OnSubjobError.

 

I have a subjob that has a tMysqlInput and I'm forcing it to fail.  However, the tLogCatcher and my OnSubjobError route isn't firing when the failure occurs - its simply going down the OnSubjobOk path.

 

Attached are a couple of screen shots on the job.  any help on understanding why this is happening would be great.

 

 

Labels (2)
1 Solution

Accepted Solutions
TRF
Champion II
Champion II

tLogCatcher catches messages from tWarn, tDie and Java exceptions, so it could be normal to not have anything from this component.
Can you explain how you force tMysqlInput to fail?

View solution in original post

3 Replies
TRF
Champion II
Champion II

tLogCatcher catches messages from tWarn, tDie and Java exceptions, so it could be normal to not have anything from this component.
Can you explain how you force tMysqlInput to fail?
Anonymous
Not applicable
Author

Thanks for the reply.

I’m forcing the failure with a syntax error in the sql code.

I’ve also tested with a delimited file not being in place with a delimited file component and again nothing.


Anonymous
Not applicable
Author

I've actually solved the issue.  I found a rogue exit in a tJava component that meant the job was silently exiting after the exception. Shifted now to tDie and all works fine.

 

Thanks