Scheduled jobs administration

<< 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


In Bizagi Management Console, you may use the Scheduler module to directly administrate Jobs which are run by the Scheduler service.

The following options are presented when using the Scheduler module.


Scheduler status

The scheduler's icon will indicate this service status (gray when stopped, crimson when started).


You may start, restart or stop the scheduler service directly from these options.

To do this, right click over the Scheduler icon and select the action (start, restart, stop). The action to execute can also be selected in the Main menu area.




The scheduler MUST BE in a started status in order to execute any scheduled jobs.




Scheduled Jobs administration

Scheduled jobs are subdivided as described in this table:


Scheduled Job type


User Jobs

User Jobs are a set of steps that can be run according to a schedule. For example, run once by specifying a specific date, or run periodically during a given interval of time. The status of these jobs can be consulted in this category.

System Jobs

Bizagi performs tasks automatically in order to ensure a proper system status. This category stores the jobs related to system maintenance tasks.

It is not recommend to manipulate the information of system jobs (they are listed for tracking and error diagnostics purposes).

Wait Jobs

Wait jobs show the status of the scheduled jobs that are related to Process Activities.

In this category we find such jobs as timers and Asynchronous Activities.

Alarm Jobs

Alarms are messages that are sent to different target groups in accordance with time criteria when an activity is about to expire, expires or has already expired. In this scheduler category, the jobs related to configured alarms are stored.


Notice that disregarding the classification above, all Jobs are presented under two lists: those waiting for execution, and those successfully executed.


Waits retries and administration

You may manage a waiting job and choose to enable it for immediate execution.



Should any wait fail (or its following transaction rollbacks), then it will be still listed in a waiting status.


Within its administration options you may also view its execution log. To review a waiting job, double-click on it:







Job Schedules

Go into this tab detail to see the list of its schedule detail (planned jobs).

Job Execution Logs

Go into this tab detail to see the log of previous executions.

Enable Job to run

Click this button to automatically enable a waiting job and set it for immediate execution. The time will be set to 10 minutes before the current time to be executed the next time the scheduler runs.



Replication Schemas Management

You may manage and reconfigure the schedules set for Replication in your project.

Within these options you may also disable the scheduled execution.





Replication administration console

You may manage a waiting job and choose to enable it for immediate execution.

This option presents the following console and options:







Replication Logs

Go into this tab detail to see the log of previous Replication synchronization executions.

Schedule Now

Click this button to automatically enable the Replication to set it for immediate execution.


Replication Schedule properties

You may review or edit the current settings for the scheduled execution.

This option presents the definition of the Replication Schedule (its properties).





For the setup presented in this tab, you may define the periodicity and frequency of execution according to the options in the table below:


Schedule option


Enable Schedule for this Replication

Mark this option for Bizagi to execute the data replication from the external source.


Mark Daily, Weekly or Monthly to define how frequently Bizagi will execute the Replication schema.

Every [...] day(s)

This modifier further defines the interval selected in the above-mentioned Periodicity option as follows.

Daily option: Enter the number of days between repetitions of the execution. Its default value is 1.


Weekly option: Enter the number of weeks between repetitions of the execution.  Also, specify on which weekdays  this schema will be executed.


Monthly option: Enter the number of months between repetitions of the execution. Additionally, select the day of the month in which this schema will be executed.

Daily frequency

Define if the execution happens once a day (and at which time), or if it should be executed at a certain time interval (minutes or hours).


Set a starting date for this schema to begin its execution.