Enabling maintenance mode
Enabling the maintenance mode stops activity on the server so you can run important tasks that require the server to be idle.
What is
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.
- Execution of processes triggered by the calendar, including recurring deployments.
- Execution of processes triggered by a repeating a process request.
- Approval or Rejection of any approval tasks.
- New version imports.
- Automatic version imports.
- Processes started upon completion of a version import.
- Auto Discovery.
- Auto Compare.
- Auto Configure.
What is not blocked during maintenance mode?
- Processes which begun before maintenance mode are allowed to run to completion.
- Sub-processes kicked off by processes that begun before maintenance mode are allowed.
- Manual tasks that are part of a process can be responded to, and the process are allowed to continue.
- Make changes to the server, such as changing properties, creating elements such as applications and resources, and editing processes.
- After maintainence mode is enabled, make sure 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.