tRouteFault doesn't continue on the Route

Six Stars

tRouteFault doesn't continue on the Route

Hi all,

 

I have a question about the tRouteFault component.

I would like to use it to catch my exception in my jobs, and send them back to the Route.

 

Here is my test Route:

Talend Data Fabric (7.1.1.20190204_0019-patch)  Sancey, Jonathan  RefCant_Nom_Tlnd (Connection Dev).jpg

 

And here is my DI job:

Talend Data Fabric (7.1.1.20190204_0019-patch)  Sancey, Jonathan  RefCant_Nom_Tlnd (Connection Dev)_2.jpg

 

I do not have particular configuration in my component, except in my cOnException:

New Message - Talend Community - Google Chrome.jpg

 

My question is: why my cOnException Route stop everytime after the first component (in this exemple, after the cSetHeader component) ?

I have tried with 2 cProcessors, it is the same problem.

New Message - Talend Community - Google Chrome_3.jpg

 

 

It seems to be caused by the tRouteFault component, because it works if I deactivate it.

New Message - Talend Community - Google Chrome_2.jpg

 

I have to use a tRouteOutput instead of a tRouteFault ?

 

Thanks in advance !

Tags (1)
Moderator

Re: tRouteFault doesn't continue on the Route

Hello,

The tRouteFault component looks exactly like tRouteOutput component but it will mark Exchange out message as fault.

Are you able to get the exact error message from your DI job?

Best regards

Sabrina

--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.

2019 GARNER MAGIC QUADRANT FOR DATA INTEGRATION TOOL

Talend named a Leader.

Get your copy

OPEN STUDIO FOR DATA INTEGRATION

Kickstart your first data integration and ETL projects.

Download now

What’s New for Talend Summer ’19

Watch the recorded webinar!

Watch Now

Talend API Designer – Technical Overview

Take a look at this technical overview video of Talend API Designer

Watch Now

Getting Started with APIs

Find out how to get started with APIs

Read