Blue Prism Scheduler: Ghost Run/Duplicate Run
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
23-12-20 06:16 PM
Hello All,
We have a peculiar issue, where a scheduled process for 2PM, is also executing at 7:30AM.
The scheduler is set for 14:00, daily, but yet, it still occurs at 7:30AM. I tried finding a duplicate schedule in our scheduler but didn't find any. In fact, the timetable lists the same specified 2PM schedule as running at 7:30AM.
Has anyone experienced this before? If so, what was going on?
Thanks!
------------------------------
Joshua Caddell
------------------------------
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-01-21 10:20 PM
Hi Joshua,
I suggest retiring the scheduler for the 14:00 PM one and let the 07:30 AM scheduler run to see what is the name and details of this scheduler. Once it executes, you can catch this unwanted scheduler and retire or delete it.
When you find and/or retire this one, you can activate the scheduler at 14:00 PM.
You can also check the scheduler in the database by using Microsoft SQL Management Studio.

------------------------------
Hossein Azimi
Customer Support Engineer, APAC
Blue Prism
Sydney NSW
------------------------------
I suggest retiring the scheduler for the 14:00 PM one and let the 07:30 AM scheduler run to see what is the name and details of this scheduler. Once it executes, you can catch this unwanted scheduler and retire or delete it.
When you find and/or retire this one, you can activate the scheduler at 14:00 PM.
You can also check the scheduler in the database by using Microsoft SQL Management Studio.
------------------------------
Hossein Azimi
Customer Support Engineer, APAC
Blue Prism
Sydney NSW
------------------------------
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-01-21 07:08 PM
Hey Hossein, thanks for the comment. We ended up doing something similar to the above by retiring the schedule and creating a new one. At this time, it doesn't appear to be an issue anymore.
The strange behavior was that the 730 schedule was already retired, but still spinning up under the 14/2PM schedule in control room (which was active in BP). For anyone who has a similar issue, the above solution should work.
------------------------------
Joshua Caddell
------------------------------
The strange behavior was that the 730 schedule was already retired, but still spinning up under the 14/2PM schedule in control room (which was active in BP). For anyone who has a similar issue, the above solution should work.
------------------------------
Joshua Caddell
------------------------------
