Mail Notification for Faulted Jobs

Feedback Orchestrator
,
1

Hi Team,

Currently we don’t have any option to notify the business users if Job is faulted(Unattended Bot machine password expired or some other reason) in Orchestrator.

It would be great if it notifies users through mail for faulted jobs. So that business users will be aware of the issue and take necessary action.

I would suggest you to add an option to enter Business user email ids under Triggers page. So that it will send mail notification to the corresponding users incase of job faulted.

1 Like
3

If your job is faulting, you need to do better error handling in your code. You should catch the error (Try/Catch), send the email, then divert to the job ending gracefully.

4

@postwick

Yes we already doing error handling in our code and getting mail notification incase of any error occurred.

Here I am talking about Technical errors like Unattended Bot machine password expired etc. In that case, Job will be faulted and we won’t receive any mail notification.

5

That’s not something a business user should be notified of. Orchestrator has alerts and will send you an email for faulted jobs, but those should go to your RPA team not business users.

6

@postwick

In my Organisation, Business users only has permission to reset the Bot machine password and we don’t have separate team to monitor the Orchestrator Jobs. It’s better to send mail notification to the Business users also along with RPA Team. So that they also aware of the issue why Bot failed.

7

If they have permissions to control robot passwords that means they have access to Orchestrator, and that means they can receive the Orchestrator alert emails for faulted jobs.

8

@postwick

They don’t have access to Orchestrator. Just they will reset the Bot machine password and will share it to the RPA Team.

10

Interesting use case. I can’t promise anything here, as it is completely up to our Orchestrator team to consider it, but I saved it for their reference.

1 Like
11

@loginerror

Thanks for the consideration :pray:

Hope Orchestrator team will implement it and release it in upcoming versions as its very useful feature to us.

12

I agree. The alerting system in Orchestrator is overly basic and should at least have granular options per job and per user, as well as the ability to add any email address as an alert subscriber.

1 Like
14

Hi @lakhsman,

Receiving built-in Orchestrator alerts is tied in to the Orchestrator membership for security reasons.

However (as I believe @postiwick is also suggesting in his first reply), you can include sending emails directly from your automation.

Alternatively and likely easier, you can add the business users to Orchestrator, setup their alerting profile (via the Manage Access page - - Open Alerts Preferences) to include the built-in “Job faulted” alert and if you need it, just disable their UI access (via the Manage Access page - - Edit - Allow Orchestrator UI Access)

1 Like
16

I see Bogdan replied already, but I do not think there is a use case here.
There is already granular control over alerts which are set per folder.

If your folders have a lot of different processes well, frankly, sounds like you should spring clean and separate them out abit. Group your folders based on business units and this is easy with alerts.