[IDEA] Add option to suppress timeout errors on TCP Sender

[mikeyw]

Is your feature request related to a problem? Please describe. NOTE: This request is related to issue #1989

TCP Sender destinations with "Queue Messages" set to "Always" and "Queue on Response Timeout" set to "Yes"(https://github.com/nextgenhealthcare/connect/issues/1989) trigger an alert when there is a timeout waiting for a response from the recipient.

Describe your use case All alerts trigger an email to support staff to investigate the issue. Read timeouts are not considered a critical issue, as long as they do not persist for more than a set period of time.

Describe the solution you'd like Two possible options:

• Add an option in the TCP Sender to suppress connection error alerts for that destination
• Update the TCP Sender logic to suppress alerts when "Queue Messages" is set to "Always" and "Queue on Response Timeout" is set to "Yes".

Describe alternatives you've considered I have tried the following solutions:

• Regular expressions in the alert configuration. Complex and not granular.
• (Current Solution) Filters in a downstream channel that sends out the alert emails. While this prevents the alert emails from being sent, it fills up the logs with lots of filtered messages.

Additional context Add any other context or screenshots about the feature request here.

[pacmano1]

This applies to any destination / connector type doesn't it? If I undertand you correctly it is sorta "don't throw an error until the final disposition of the message (or maybe destination) is known". 100% agree with the ask.

[mikeyw]

@pacmano1 Exactly!