Scheduler 2.0

<< Click to Display Table of Contents >>

Navigation:  Automation Server > Automation Server configuration and administration guide > System maintenance and monitoring > Environment settings and administration > Management Console > Scheduled jobs administration >

Scheduler 2.0


In large projects that demand high performance, and availability for the execution of a considerable number of jobs, you have the possibility to upgrade the Scheduler version. You can update the Bizagi Scheduler to increase the performance using multithreading capabilities, enhance reliability, and execute queued jobs considering a priority. The new Scheduler, also called Scheduler 2.0, has the following characteristics:


Jobs are always executed using queues; this avoids clogs or deadlocks of those jobs.

Jobs are queued using priority.

Updating the Scheduler to the 2.0 version is transparent to end-users.

After upgrading the Scheduler, there is no further configuration required in any Scheduler.


The following document presents the configuration procedure to upgrade the Scheduler to the 2.0 version and a description of priorities handled by this.


Are you eligible to update to Scheduler 2.0?

From version 11.2.5, Bizagi released the Scheduler 2.0. This Scheduler version helps to execute job priorities in a more efficient way. It is very important to keep in mind that once you upgrade to Scheduler 2.0, there is no turning back to version 1.0. Therefore, your decision to upgrade must be analyzed carefully, considering the following scenarios:


Auto tune the Scheduler

Version 2.0 of the Scheduler does not need any tuning because it manages automatically a queue of jobs based on their priority. Therefore, if you do not need to tune your Scheduler manually, and want to rely on automatic tuning, you can upgrade the version.


Prioritize execution of automatic tasks

Scheduler 2.0 prioritizes the execution of automatic asynchronous tasks based on the priority set in the task:



If you want to rely on this capability, you are eligible to upgrade to version 2.0 of the Scheduler.


Update maintenance jobs using a REST API

Version 2.0 has a REST API that lets you configure some parameters of the maintenance tasks executed by the Scheduler. Refer to Scheduler 2.0 API.


Automatic setup in a cluster infrastructure

If you need to add a new server in a cluster configuration, as explained here, version 2.0 of the Scheduler no need for extra configuration when you add the new Scheduler node.


Upgrading Procedure

Customers must request upgrading to the Scheduler 2.0 through a support ticket. Our team must analyze if you are eligible to upgrade to the 2.0. If you are the Bizagi team will guide you to the upgrading procedure.



The Scheduler 2.0 is available from version 11.2.5 for Automation and On-premises projects. You can upgrade your Scheduler anytime through a support ticket. Once upgraded, this cannot be undone.



Jobs Priority

The Scheduler 2.0 executes jobs considering their priority. The priority can be set depending on the job type and is defined as follows:


Job Type



Business Processes jobs

The following elements configured in Bizagi Studio or the Work Portal:



User jobs

It is predefined as high and cannot be changed.

Asynchronous activity jobs

Invocation and retries of Web Services, Connectors or Bots in Services tasks or Bots tasks as Asynchronous Activities executed by the Scheduler.

You can define the priority on the task properties set in the model.



System jobs

Jobs executed by the Scheduler for system maintenance as described at Scheduled jobs administrator , LDAP synchronization and replication jobs.

These jobs are executed by default at 10pm everyday. but you can change the time using the API of the Scheduler 2.0.


Tuning the Scheduler 2.0

The Scheduler 2.0 handles automatically the logic to execute jobs the fastest and efficient way possible . This version 2.0 executes jobs based on the priority and load of each Scheduler. This version uses multithreading capabilities of the CPU and executes multiple jobs considering the priority and job type. Additionally, jobs are queued. That is, the Scheduler never clogs jobs. If by any reason a job is not executed successfully, it is queued and later retried considering the priority. Therefore no tuning is needed.



Fine tuning the Scheduler 2.0 is not necessary, therefore, the tuning keys do not apply when using the version 2.0.


The Scheduler 1.0 has the option to fine tune the performance using keys, refer to How to fine tune the Bizagi Scheduler. In the Scheduler 2.0 version, these keys are obviated. Any configuration set on these keys has no impact upon the Scheduler 2.0 performance, and it remains using the queuing logic previously described.


Maximum number of threads used by the Scheduler 2.0

The Scheduler 2.0 uses a maximum number of worker threads of your processor based on the following calculation:

Number of logical processor count * 5


It is the number of logical processors available in the machine times 5. Refer to logic processor definition. By default, this value cannot exceed 20 worker threads.


If you need to configure a value greater than 20. You can use the following key:

<key="SchedulerWorkerCount" value="20"/>


Open the config file, BizAgi.Scheduler.Services.exe.config, of the Scheduler, usually located in:




If used, this key overwrites the calculation of the number of processors times 5.