<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How to prevent the Job from dying on Error in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/How-to-prevent-the-Job-from-dying-on-Error/m-p/2352857#M119164</link>
    <description>some components have "Die on Error" check-box, some - not
&lt;BR /&gt;also this checkbox not help with Null-pointer errors
&lt;BR /&gt;
&lt;BR /&gt;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</description>
    <pubDate>Wed, 22 Mar 2017 10:07:42 GMT</pubDate>
    <dc:creator>vapukov</dc:creator>
    <dc:date>2017-03-22T10:07:42Z</dc:date>
    <item>
      <title>How to prevent the Job from dying on Error</title>
      <link>https://community.qlik.com/t5/Talend-Studio/How-to-prevent-the-Job-from-dying-on-Error/m-p/2352856#M119163</link>
      <description>&lt;P&gt;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.&lt;BR /&gt;&lt;BR /&gt;My problem is that I'm trying to make the job&amp;nbsp;error resistant. Like if the connection to file server down, then simply log the error and continue to process other stuff.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;However, every time I get a error, the job&amp;nbsp;keeps dying. I can catch the error using tAssetCatcher or tLogCatcher but it doesn't stop the job from dying.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Is there a way to do "try catch" on components?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 22 Mar 2017 09:46:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/How-to-prevent-the-Job-from-dying-on-Error/m-p/2352856#M119163</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-03-22T09:46:04Z</dc:date>
    </item>
    <item>
      <title>Re: How to prevent the Job from dying on Error</title>
      <link>https://community.qlik.com/t5/Talend-Studio/How-to-prevent-the-Job-from-dying-on-Error/m-p/2352857#M119164</link>
      <description>some components have "Die on Error" check-box, some - not
&lt;BR /&gt;also this checkbox not help with Null-pointer errors
&lt;BR /&gt;
&lt;BR /&gt;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</description>
      <pubDate>Wed, 22 Mar 2017 10:07:42 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/How-to-prevent-the-Job-from-dying-on-Error/m-p/2352857#M119164</guid>
      <dc:creator>vapukov</dc:creator>
      <dc:date>2017-03-22T10:07:42Z</dc:date>
    </item>
  </channel>
</rss>

