Recurring tasks can be created to place the server in lockdown mode and take the server out of lockdown mode. These tasks are useful for scheduling other tasks while the server is mostly idle and not accepting connections from clients.

While in lockdown mode, the server will report itself as unavailable, and will also reject requests from any user that doesn't have the lockdown-mode privilege. The recommended flow for a recurring task chain that uses lockdown mode would be:

  1. Enter lockdown mode task.
  2. Delay task that waits for the work queue to report that the server is idle.
  3. Desired tasks to perform while the server is in lockdown mode.
  4. Leave lockdown mode task.

The enter and leave lockdown mode tasks each have one optional property that can be used to supply a description for why that the server is being placed in this mode.