Blue Prism Scheduler
Blue Prism contains a system which can be used to execute processes at specified times and repeat their execution at various intervals. The scheduler runs as part of a configured Blue Prism Server service which has access to the Blue Prism environment with the processes held in it.
The schedules can be configured to run once, or be repeated at minutely, hourly, daily, weekly, monthly or yearly intervals. Calendars can be employed to cause the schedule to run only on working days, skipping specific certain weekdays and/or public holidays.
To find out more check out the Guide to Scheduler in the Related Documents section below.
Troubleshooting
- Ensure that you haver version 3.5, or later, of Blue Prism installed
- Ensure that you have the correct permissions to perform this action. Contact your System Administrator to check / add permissions.
Ensure that the Blue Prism Server service has been restarted since you made your changes. The changes will not be activated until the service is restarted. Remember to ensure that no sessions are running before restarting the service
- Ensure that you haver version 3.5, or later, of Blue Prism installed
- Ensure that you have the correct permissions to perform this action. Contact your System Administrator to check / add permissions.
- Ensure the Blue Prism Server service is running. This is required to trigger schedules.
- Ensure the resource(s) on which the task(s) are scheduled to run were on-line at execution time.
- Ensure the resource(s) on which the task(s) are scheduled to run are public resource PC’s.
- Ensure the schedule isn’t configured to run on a date that doesn’t exist in the month (e.g. configured to run on the 31st of the Month and it was not executed in April).
- Ensure the schedule is configured to run on the correct day of the week. Remember, to Blue Prism, the first day of the week is always Monday and the last day of the week is always Sunday.
- Ensure the day(s) on which the schedule has not executed is (are) configured to be a working day(s) in the calendar being used by the schedule.
- Has the resource, on which the session has been scheduled, been subsequently moved to a Resource Pool? A schedule can only be run on a Resource Pool or a specified VM that is not part of a Resource Pool. A schedule originally configured to run a specified resource, which is subsequently been moved to a Resource Pool will fail.
- Ensure that multiple processes, scheduled to run on the same resource concurrently, are able to run concurrently. If multiple processes are scheduled to run on the same resource, and any of the processes are exclusive, the task will be terminated as the resource is too busy to run anything other than the exclusive process.
- Ensure the domain, on which the target Resource PC is hosted, is included in the application server’s domain suffix search list. The Blue Prism Scheduler runs on the application server. When a schedule is triggered, the Scheduler sends a TCP/IP message to the Resource to start the schedule using the host name of the Resource. If the Resource PC is hosted on a different domain to the application server, the host cannot be found if the domain on which the target Resource PC is hosted is not included to the application server’s domain suffix search list.
- Do the sessions all belong to the same task? A failure of any session within a task, will cause the whole task to fail. Therefore, If multiple sessions are scheduled, a failure of any of these sessions will cause all the other sessions to terminate.
- Uncheck the “Fail Fast on Errors” option
Ensure the Startup parameters have been input correctly in the task.
Visit Blue Prism Help online to find more information on the latest product features, troubleshooting advice and 'how to' guides.