Preview Tool

Cisco Bug: CSCur68758 - Poor failure handling in Email Actions

Last Modified

Sep 14, 2018

Products (2)

  • Cisco Workload Automation
  • Cisco Tidal Enterprise Scheduler 6.2

Known Affected Releases


Description (partial)

We have had issues recently with the way that TIDAL handles email notifications. When an action is configured with multiple email addresses, it opens an SMTP connection for each address. However, when one address fails, the entire action fails (550 5.7.1 Unable to relay)

1) We need to know when an action has failed. Either a configurable email address where TIDAL sends all internal failure messages, or something in the GUI that alerts us. 

2) When a single email (out of possibly dozens) fails, this should not cause the entire action to do nothing. Note the failure, and send to the remaining recipients.

TES 6.2.1
Email Actions

1) Create Email Action with multiple addresses, including one outside the domain.
2) Configure SMTP server to disable relay (outside of domain).
2) Trigger the Action.
3) Observe the entire Action fail because the one external domain email cannot be sent.
4) Observe log messages similar to the following:

10/30 06:51:28:453[49:EV-8]: (mem=1432163080/2130706432) SMTPSender: Could not send email (SUCCESS D-EDWCONTROL-OFLevel4End) reason: Failed to send email.  Mail server responded : 550 5.7.1 Unable to relay
10/30 06:51:28:454[49:EV-8]: (mem=1432126784/2130706432) SchedulerPrimaryKeyFactoryImpl: Assigned primary key 24210689 for new record type 'MessageLog'
10/30 06:51:28:483[49:EV-8]: (mem=1432077104/2130706432) SMTPSender: Failed to send email.  Mail server responded : 550 5.7.1 Unable to relay Failed to send email.  Mail server responded : 550 5.7.1 Unable to relay
                at com.tidalsoft.adapters.smtp.SMTPSender.sendln(
                at com.tidalsoft.adapters.smtp.SMTPSender.sendEmail(
                at com.tidalsoft.adapters.smtp.SMTPAdapter.send(
                at com.tidalsoft.scheduler.logic.handlers.EmailHandler.execute(
                at com.tidalsoft.scheduler.logic.ActionMessageHandler.onExecute(
                at sun.reflect.GeneratedMethodAccessor138.invoke(Unknown Source)

                at sun.reflect.DelegatingMethodAccessorImpl.invoke(
                at java.lang.reflect.Method.invoke(
                at com.tidalsoft.framework.message.MessageRouter$MessageMethod.invoke(
                at com.tidalsoft.framework.message.MessageRouter._route(
                at com.tidalsoft.framework.message.MessageRouter.route(
                at com.tidalsoft.framework.message.BaseMessageHandlerImpl.onMessage(
                at com.tidalsoft.framework.message.MessageDispatcher$

10/30 16:55:04:477[43:EV-2]: (mem=1543073664/2131755008) SMTPSender: sending to SMTP server: RCPT TO: <>
10/30 16:55:09:479[43:EV-2]: (mem=1541628976/2131755008) SMTPSender: response from SMTP server: 550 5.7.1 Unable to relay
10/30 16:55:09:482[43:EV-2]: (mem=1541575640/2131755008) SMTPSender: Failed to send email.  Mail server responded : 550 5.7.1 Unable to relay
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.