Maintenance Mode
Maintenance mode lets administrators temporarily pause all pipeline executions across the platform. While active, no new pipelines will start, giving you a safe window to perform system updates, database migrations, or other infrastructure work without risking data inconsistency.
Open the page from System Management > Maintenance tab.
Status Banner
The top of the page shows a prominent status banner indicating the current system state:
- System Operational — All systems are running normally. Pipelines can be executed.
- Maintenance Mode — The system is on hold. No new pipelines will start until maintenance is complete. The reason provided when maintenance was enabled is displayed below the status.
Click Refresh to reload the current status from the server.
Enabling Maintenance Mode
Toggle the Maintenance Mode Control switch from Operational to Maintenance. A confirmation dialog appears asking you to provide a reason for enabling maintenance mode (required, up to 500 characters). Example reasons:
- "Scheduled system updates"
- "Database migration in progress"
- "Infrastructure maintenance"
After confirming, maintenance mode takes effect immediately. All connected clients are notified of the status change in real-time via WebSocket, and the pipeline engine stops accepting new executions.
Enabling maintenance mode prevents all new pipeline executions from starting. Ensure that any time-critical pipelines have completed before activating this mode. Already-running pipelines are not forcefully stopped — they are allowed to complete.
Disabling Maintenance Mode
Toggle the switch back from Maintenance to Operational. A confirmation dialog asks for a reason for disabling maintenance mode (e.g. "Maintenance completed"). Once confirmed, the system returns to normal operation and pipelines can be executed again.
Always provide a meaningful reason when enabling or disabling maintenance mode. The reason is recorded in the history log and helps your team understand past maintenance events during audits or troubleshooting.
Maintenance History
Below the toggle control, a Maintenance History table tracks every maintenance mode change. Each entry shows:
| Column | Description |
|---|---|
| Status | A color indicator — red for enabled, green for disabled. |
| Action | Whether maintenance mode was enabled or disabled. |
| Reason | The reason provided by the administrator. |
| Timestamp | The date and time of the change. |
| User | The administrator who made the change. |
The history is paginated if there are many records. Use the Previous and Next buttons to navigate between pages.
How It Works
When maintenance mode is enabled:
- The organization settings are updated and the change is recorded in the settings history.
- A maintenance event is published to the internal event bus.
- The pipeline engine and other modules receive the event and stop accepting new executions.
- All connected browser sessions are notified in real-time, so every user sees the updated status without refreshing.
When maintenance mode is disabled, the reverse occurs — modules resume normal operation and clients are notified.