https://community.qlik.com/t5/Talend-Studio/Is-it-possible-to-catch-a-DB-error-and-avoid-an-interation-to/m-p/2195646#M155 Hello Hideki-san <BR />You could put the database processing and the error handling snippet inside a child job and then clear the die on error message. &nbsp;I think that would allow you to continue processing. <BR />Ed Thu, 05 Jan 2017 17:18:17 GMT Anonymous 2017-01-05T17:18:17Z https://community.qlik.com/t5/Talend-Studio/Is-it-possible-to-catch-a-DB-error-and-avoid-an-interation-to/m-p/2195645#M154 <P>Hi,<BR />I have the following job, where I am iterating on a table list to read data from each table.<BR />Sometimes, the select statement throws an Exception, which I would like to handle and continue iterating on the other tables.<BR /><IMG src="https://community.qlik.com/" border="0" />The "OnComponentError" trigger doesn't answer the problem because the the processing will continue on that trigger branch but the iteration is aborted.<BR />Do we have a solution to error catching in DB components ? How would you implement such a demand ?<BR />Thanks&nbsp;</P> Thu, 05 Jan 2017 17:10:33 GMT https://community.qlik.com/t5/Talend-Studio/Is-it-possible-to-catch-a-DB-error-and-avoid-an-interation-to/m-p/2195645#M154 Anonymous 2017-01-05T17:10:33Z https://community.qlik.com/t5/Talend-Studio/Is-it-possible-to-catch-a-DB-error-and-avoid-an-interation-to/m-p/2195646#M155 Hello Hideki-san <BR />You could put the database processing and the error handling snippet inside a child job and then clear the die on error message. &nbsp;I think that would allow you to continue processing. <BR />Ed Thu, 05 Jan 2017 17:18:17 GMT https://community.qlik.com/t5/Talend-Studio/Is-it-possible-to-catch-a-DB-error-and-avoid-an-interation-to/m-p/2195646#M155 Anonymous 2017-01-05T17:18:17Z