Managing errors in the input node

• If the node detects an internal error before the message is propagated to the Out terminal, the node always propagates the message and an exception list to the Failure terminal if the node has a Failure terminal and if you have connected a fail flow. If the Failure terminal is not connected or an exception occurs downstream of the failure terminal, the transaction is rolled back.
• If you connect the Catch terminal (if the node has one), this indicates that you want to handle all exceptions that are generated in the out flow. If you do not connect the Catch terminal, or the node does not have a Catch terminal, or an exception occurs downstream of the Catch terminal the current transaction is rolled back.
• Any internal exceptions that occur in the node after the message has been propagated to the Out terminal cause a rollback of the transaction. This situation is rare but could happen for some input nodes.

Refer to the documentation for each input node to determine the effect of rolling back the transaction and also for the retry capabilities provided by some input nodes.