topic RE: Blue Prism Schedule Monitor in Digital Exchange

Blue Prism Schedule Monitor

Prathamesh_ — Tue, 29 Nov 2022 14:45:00 GMT

Hi On Schedule Monitor tool that is provided by Blue prism I Had few queries. Can anyone help in answering this?
1) Does the schedule monitor detect terminations as well or it just alerts only for schedule misses?
2) Currently there is no rerun mechanism in the tool, is there any way to customize it to add rerun mechanism, which will trigger the failed schedules.
3) Is there any script or code associated with Blue Prism schedule monitor tool? and how can we view and modify it?

------------------------------
Prathamesh .
------------------------------

RE: Blue Prism Schedule Monitor

Tejaskumar_Darji — Wed, 30 Nov 2022 06:29:00 GMT

Hello Prathamesh,

1) It supports Failure Type of Malfunction which is nothing but session termination due to some exceptions.

2) As this is an external monitoring tool that uses Windows Task Scheduler and is not a built-in function, hence I would recommend finding another approach to trigger the session once the notification email is received from Schedule Monitor. Also, you can create a scheduler accordingly to trigger it every X minutes. If failed what to do next etc in consequent tasks within the schedule manager.

3) Check out the full details here on DX for this asset.

------------------------------
If I was of assistance, please vote for it to be the "Best Answer".

Thanks & Regards,
Tejaskumar Darji
Sr. Consultant-Technical Lead
------------------------------

RE: Blue Prism Schedule Monitor

charliekovacs — Thu, 01 Dec 2022 18:54:00 GMT

Hi Prathamesh,

Tejaskumar has provided good insight to your questions. I will elaborate on a few points.

1. The Schedule Monitor detects two types of problems that can occur with the Scheduler:

Misfires: Scheduler fails to start a scheduled process (eg. Scheduler not running, time zone change)
Malfunctions: Scheduler successfully starts a scheduled process, but the process fails during execution (logic error, Runtime Resource is offline, etc.)

2. Re-running misfired or malfunctioned schedules is not a capability in the Schedule Monitor currently, butTejaskumar has good advice about solving this, particularly building failover logic into the design of the processes and schedules.

3. Yes, with Schedule Monitor v1.2.0, the source code is now available. https://digitalexchange.blueprism.com/dx/entry/9648/solution/blue-prism-schedule-monitor

------------------------------
Charlie Kovacs
Sr. Digital Exchange Engineer
Blue Prism
Austin, USA
------------------------------

RE: Blue Prism Schedule Monitor

KarthikChandra2 — Fri, 02 Dec 2022 14:50:00 GMT

Thanks @Charlie Kovacs

Appreciate your quick turnaround for the New Release! It Works Now

Looks like we are greeting all the missed/misfired schedules stored in the Database, is it possible for us to get the missed/misfired schedules based on the given dates or for the recent week/day else every time we are getting the complete logs in the mail from the Database which in our case is 25 MB every time in each mail.

Also, can these logs in email can be saved locally instead of emails.

Thanks!
Karthik Chandrasekaran

------------------------------
Karthik Chandrasekaran
------------------------------

RE: Blue Prism Schedule Monitor

charliekovacs — Fri, 02 Dec 2022 18:42:00 GMT

Hi Karthik,

The first run of the Schedule Monitor will send a complete history of failed schedules. Then it should be incremental so that only newly failed schedules will be sent in subsequent emails. You should not be getting a complete history every time the Schedule Monitor runs. And you should not be getting emails at all (after the first one) unless there is a newly failed schedule.

Do you have the Schedule Monitor and Blue Prism database installed on different computers? And are those computers set to different time zones?

Can you share:
1. The time that the first email was received
2. The [Scheduled Runtime] value of the last failed schedule in that first email

As for receiving the failed schedule report, email is the only method in the Schedule Monitor currently. It looks you have a use case where email is not ideal because of a) size limits and b) wanting a local log file that can perhaps be monitored automatically.

I will take a look at an update to the Schedule Monitor that gives more choices for outputting the report.

------------------------------
Charlie Kovacs
Sr. Digital Exchange Engineer
Blue Prism
Austin, USA
------------------------------

RE: Blue Prism Schedule Monitor

KarthikChandra2 — Mon, 05 Dec 2022 06:51:00 GMT

Hi Charlie,

Please find our response inline in Bold.

The first run of the Schedule Monitor will send a complete history of failed schedules. Then it should be incremental so that only newly failed schedules will be sent in subsequent emails. You should not be getting a complete history every time the Schedule Monitor runs. And you should not be getting emails at all (after the first one) unless there is a newly failed schedule.

<KC> We are receiving complete output every time when the Schedule Monitor triggers, and it doesn't look like incremental in our case. Yes, there are new failed schedule before the next trigger (this means, we will be receiving complete output every time (please clarify).

Do you have the Schedule Monitor and Blue Prism database installed on different computers? And are those computers set to different time zones?

<KC> We are using Azure SQL Managed Database and both DB / Blue Prism are in the same time zone (CET).

Can you share:
1. The time that the first email was received <KC> (12 Dec 22 07:53 AM CET)
2. The [Scheduled Runtime] value of the last failed schedule in that first email

Thanks!
Karthik Chandrasekaran

------------------------------
Karthik Chandrasekaran
------------------------------

RE: Blue Prism Schedule Monitor

KarthikChandra2 — Tue, 06 Dec 2022 12:15:00 GMT

Hi @Charlie Kovacs

Application is working as expected.

We observed that 5 mins trigger on the application is providing us the complete hence updated the trigger frequency to 1 hour, which is now providing us the missing/misfire schedule only from the past runs (PFA)

If you could check and accommodate the below in the new version which would be more helpful.

* Segregating missing schedules & misfire schedules in separate emails.
* Missing/misfire schedules in between a time slot.

------------------------------
Karthik Chandrasekaran
------------------------------