The TimeoutNotification node takes the following actions when it handles errors with transactional messages. Errors encountered with non-transactional messages are handled as described in Managing errors in the input node.
This action is summarized in the table below:
Error event | Failure terminal connected | Failure terminal not connected | Catch terminal connected | Catch terminal not connected |
---|---|---|---|---|
Node detects internal error | Flow connected to the Failure terminal handles the error | Error logged, node retries | Not applicable | Not applicable |
Node propagates message to out terminal, exception occurs in out flow | Not applicable | Not applicable | Flow connected to the Catch terminal handles the error | Error logged, node retries |
Node propagates message to Catch terminal, exception occurs in flow connected to the Catch terminal | Error logged, node retries | Error logged, node retries | Not applicable | Not applicable |
Node propagates message to Failure terminal, exception occurs in flow connected to the Failure terminal | Not applicable | Not applicable | Error logged, node retries | Error logged, node retries |
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac30140_ |