Job Template Error Settings

From the Inbound Job Templates and Outbound Job Templates tabs, you can override ETL error settings. To override:

1. Select a job template (row) to override
   
2. Click the Job Template Error Settings button on the toolbar to bring up the Job Template Error Settings dialog
   
   1. The settings button is grayed out unless a job templates (row) is selected
      
      
   2. The settings function is only available to users in the Administrator security group
3. Check a setting to override the default inherited from the ETL error settings
   
   1. Fields available
      1. API: No enumerated keys were found in your data – No enumerated keys were found in your data
      2. API: There is no outbound data to send – There is no outbound data to send
      3. API: There was an error authorizing – There was an error authorizing
      4. API: There was an error connecting – There was an error connecting
      5. API: There was an error returned from your API call – There was an error returned from your API call
      6. DATABASE: There was a database error – There was a database error
      7. FILE: A previously ran file was not processed – A previously ran file was not processed
      8. FILE: The data set is empty and allow empty tables is off – The data set is empty and allow empty tables is off
      9. FILE: There was an error with a file or path – There was an error with a file or path
      10. FTP: The FTP connection failed – There was a connection failure
      11. FTP: The FTP login failed – There was a login failure
      12. FTP: The remote path was not found – The remote path was not found
      13. FTP: Unable to download FTP file – Unable to download file
      14. GENERAL: There was an error during data mapping – There was an error during data mapping
      15. GENERAL: There was an error running an external script – There was an error running an external script
      16. GENERAL: Unable to run script – Unable to run script
      17. PARSING: Data node was not found – Data node was not found
      18. PARSING: There was an error parsing your json data – There was an error parsing your JSON data
      19. PARSING: There was an error parsing your xml data – There was an error parsing your XML data
      20. PARSING: Your data will exceed the maximum allowed tables – Your data will exceed the maximum allowed tables
4. Enter or select a value for each error setting
   1. Fatal Error: Stop All Future Runs
   2. Retry: Try for 3 Runs Before Fatal Error
   3. Ignore: Will Not Affect Future Runs
5. Click the Update button when finished to update the inbound job template. You will be redirected back to the Inbound Job Templates or Outbound Job Templates tab. Click the Close button to cancel the operation.