Maintenance mode provides an option for the user to either stop all the activities in the Bot Manager (Server Maintenance) or down all the robots connected to a machine(s) for maintenance (Machine Maintenance).
An icon labeled “Maintenance Mode Trigger” can be found inside the Trigger. On clicking that, the user will be navigated to the “Add Maintenance Mode Trigger” window. Several fields can be found in this window such as Name, Schedule Type, Maintenance For, Frequency and Daily Frequency.
Name: Provide a name for the maintenance mode trigger as per their preference.
Schedule Type: “Recurring” is the only default value available for this field.
Enabled: The “Enabled” check box must be selected for the Maintenance Trigger to run; otherwise, the maintenance activity will not begin to execute.
Refresh Last Scheduled DateTime: This checkbox enables the user to reset the last scheduled date time i.e. change it to null. This can be beneficial if a user wants to run the trigger again.
Maintenance For: The user can select whether they will be performing Server Maintenance or Machine maintenance through this field. This feature will move the Robot or Server to an offline state based on the frequency set while creating the trigger for Maintenance.
Machine Maintenance: All robots connected to the particular machine will undergo maintenance.
Server Maintenance: This will temporarily bring down the specific Bot Manager environment and no activities can be performed.
Tags: This field allows to enter a relevant tag name for easy filtering in Bot Manager. (Optional)
Frequency: There are two options for configuring this field –
The “Occurs” dropdown menu, from which the user can specify whether the maintenance should happen Daily, Weekly or Monthly.
The “Recurs Every” option is used to specify the interval at which the Maintenance trigger should be executed based on the selected option (daily, weekly or monthly).
Note: Refer to the Time scheduler to understand the configuration of the frequency field.
Daily Frequency: This field has three options –
The “Starting at” option signifies the time at which the trigger should start.
The “Expiry Time” indicates the end time of the maintenance activity.
User can either “Stop” the maintenance or make a “Request” to stop the Maintenance through the “Stop Request Type” field.