What's the best way to route an error to an error view AND stop that portion of the pipeline when it happens?

·Apr 08, 2026 07:04 PM·

What's the best way to route an error to an error view AND stop that portion of the pipeline when it happens? i.e. if an error occurs, I want to pass to error to the error view and not execute the child pipeline

✅1

4 comments

· Sorted by Oldest

SnapLogic Best Practices

What's the best way to route an error to an error view AND stop that portion of the pipeline when it happens?

Milo P.

·Apr 08, 2026 07:04 PM·

What's the best way to route an error to an error view AND stop that portion of the pipeline when it happens? i.e. if an error occurs, I want to pass to error to the error view and not execute the child pipeline

✅1

4 comments

· Sorted by Oldest

Milo P.
·
·
I added a filter snap which seems to have worked! $input0 != null && $input0.length > 0
👍1
Joël B.
·
·
Hi Milo P., I faced this case, and instead of the Gate snap, I use the Group By N snap with N = 0: it groups its inputs, and outputs nothing if no input was received. 🙂 (You could also activate the "ignore empty input" checkbox in the Gate snap)
Milo P.
·
·
Here Joël is again saving the day 🙂 Thank you!
Milo P.
·
·
Out of interest, why do you use Group By N vs Gate?

Milo P.
·
·
I added a filter snap which seems to have worked! $input0 != null && $input0.length > 0
👍1
Joël B.
·
·
Hi Milo P., I faced this case, and instead of the Gate snap, I use the Group By N snap with N = 0: it groups its inputs, and outputs nothing if no input was received. 🙂 (You could also activate the "ignore empty input" checkbox in the Gate snap)
Milo P.
·
·
Here Joël is again saving the day 🙂 Thank you!
Milo P.
·
·
Out of interest, why do you use Group By N vs Gate?