Thanks Bill. I did open a ticket and found resolution through support.
Looks like the smtp userid/password are required for workflow failure notifications. This wasn't clear and could be improved.
Couple things that could be done better on this via an enhancement request perhaps?
- The dialog where you configure doesn't make smtp auth a requirement. It all appears to work (sending emails via plugin in a workflow) but for failures it did not.
- Support also noted that my template was "customer built". This was copied from Hitachi template - which also didn't notify of failures because of the smtp auth requirement. Why is SMTP authentication required for this feature? Support recommended adding shared service properties - if so, should these have been there and not have to ad them?.
Long story short - notifications of workflow failures should be core functionality and simple. This was not that simple or clear. Maybe for someone who built the product - but needs to be clear and easy for customers.