Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Unable to send email due to : Invalid Addresses



Unable to send Email when using the SendEmailNotification activity.

Error Messages

Caught unhandled exception : Unable to send email due to : Invalid Addresses

Steps to Reproduce

  1. Configure an Email account set up which uses the Global Resource settings for the email address and user ID in the Sender details. The Test connectivity must be good.
  2. Configure an activity in the PostProcessing of a case.
  3. Call the SendEmailNotification activity in the activity that is configured in the PostProcessing of a case.
  4. Run the case.


In this case, the pyNotifyAccountName parameter is the assigned value of the Accountname before the SendEmailNotification is invoked.
The SendEmailNotification activity expects all the parameters which are Required to send an email on the Parameter page with the resolved values.
However, there is extra handling for the pynotifyAccountName paramater. If this parameter has a value, then all the Parameter page values will be overwritten with the actual email account details (it can have values with GRS syntax. Additionally, in this case, the GRS will not be resolved or dereferenced). 
When an account name is provided, there is no handling involved to resolve values with GRS syntax in the SendEmailNotification activity. If this database Open has values with GRS syntax, the values are not resolved in this activity. Instead, the values are sent directly to the sendEmail engine API, where it fails.


Perform the following local-change:

Set pyNotifyAccountName to empty prior to invoking the SendEmailNotification activity.

Published August 19, 2019 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us