Customize email recipients when bots unsuccessfully deploy

​@jtowle Using the Try … Catch actions, you can have the automation itself to send an email to a person, persons, or a distribution group (set up by your email administrator) if the automation fails. It’s probably best to not rely on the Control Room picking up errors from bot runs to send emails. Why? Try … Catch masks the error and could make a failed bot run look like it succeeded.

​@Aaron.Gleason Thanks for the response. We do implement try catch activities within all of our automations. The scenarios we are encountering do not allow for execution of the catch sections within the bots themselves.

On failed deployments the bot does not open/activate and does not execute any actions, therefore, we only receive the default error email notification from control center that a bot failed deployment (sent only to the user who set up the schedule/bot run).

On bot-run timeouts, a good example is if there is a message box within the workflow that runs on a virtual machine. The bot is stuck on the message box and times out, closing without executing any closing/catch actions. Again, we only receive the default error email notification from control center that a bot timed out (sent only to the user who set up the schedule/bot run).

We would like to update the default error email notification from control center to send to the entire team instead of just the user who set up the schedule/bot run. Thanks.