Enabling maintenance mode

Enabling the maintenance mode stops some activities on the server for a specific duration so you can run important tasks that require the server to be idle.

Ensure that you have the permissions to manage maintenance mode.

When you enable maintenance mode, users can log in to the server as usual and perform some limited tasks. A message is displayed at the top indicating the start and estimated end time of the maintenance activity. While the maintenance mode is enabled, some of the tasks/actions are blocked and some are allowed. Below is a list of such tasks:

Tasks blocked during maintenance mode	Tasks not blocked during maintenance mode
Execution of new global, component, and application processes. With additional permissions, you can allow users to execute new deployments while maintenance mode is enabled.	Processes which are started before maintenance mode are allowed to run for completion.
Execution of processes triggered by the calendar, including recurring deployments.	Sub-processes kicked off by processes that are started before maintenance mode are allowed.
Execution of processes triggered by a repeating a process request.	Manual tasks that are part of a process can be responded to, and the process are allowed to continue.
Approval or rejection of any approval tasks.	Making changes to the server, such as changing properties, creating elements such as applications and resources, and editing processes.
New version imports.	-
Automatic version imports.	-
Processes started upon completion of a version import.	-
Auto Discovery.	-
Auto Compare.	-
Auto Configure.	-

Click Settings > System Settings.
Activate the Enable Maintenance Mode option in the General Settings field.
Save the settings.

The maintenance mode is enabled.

After maintenance mode is enabled, make sure that you do not restart the server until all processes have completed.
After the maintenance schedule ends, you must disable the Enable Maintenance Mode option manually.