Maintenance Mode

Maintenance mode pauses one organization's work so you can upgrade equipment, migrate a database, or do other planned work safely. It applies to a single organization. Other organizations on the same instance keep running.

While maintenance mode is on for an organization:

• Pipelines: no new pipeline work starts. Triggers, schedules, webhooks, manual runs, retries, node emits and queued items are held back. Pipeline executions that are already running when you turn maintenance on are sent a cancellation. They do not run to completion.
• Connections: every connection in the organization is suspended. Nothing is deleted. While maintenance is on, nobody can start or resume the organization's connections. They are told that the organization is in maintenance.

When you turn maintenance mode off, pipeline work can start again and the connections that maintenance suspended are resumed automatically. Connections that someone had already suspended or stopped before maintenance began stay as they were.

Where to find it

• Organization Overview: the status pill in the page header, next to the organization's name, shows Operational or Maintenance. Click it to open the Maintenance Mode dialog. Every member of the organization can see the state.
• Maintenance banner: while maintenance is on, a banner at the top of every page says so. Its Manage button opens the same dialog.
• Organizations list (platform administrators): each organization's actions menu has Enter maintenance or Exit maintenance. You can turn maintenance on or off for any organization without switching to it. An organization in maintenance shows In maintenance in the list, with its reason.

Only users who can update the organization (Organization.Admin, or a platform administrator) can turn maintenance mode on or off. For everyone else the switch is disabled, with a note explaining why.

Enabling Maintenance Mode

1. Open the Maintenance Mode dialog from the Overview pill, or choose Enter maintenance in the Organizations list.
2. Move the switch from Operational to Maintenance.
3. The confirmation dialog lists what will happen: running pipeline executions are cancelled, new pipeline work is held back, and every connection is suspended. Enter a reason (required, up to 500 characters), for example "Scheduled system updates" or "Database migration in progress".
4. Click Enable Maintenance Mode.

Maintenance mode takes effect immediately. Every open browser session sees the change within about 30 seconds.

warning

Turning maintenance mode on cancels the pipeline executions running in the organization at that moment. Work those executions already completed stays done, such as database writes, published messages and API calls. Before you turn maintenance on, make sure that no time-critical pipeline is partway through.

Disabling Maintenance Mode

Move the switch back from Maintenance to Operational, or choose Exit maintenance in the Organizations list. Enter a reason (for example "Maintenance completed") and confirm. Pipeline work can start again, and the connections that maintenance suspended are resumed.

tip

Always give a meaningful reason. It is recorded in the maintenance history and helps your team understand past maintenance windows during audits or troubleshooting.

Connections during maintenance

On the Connections page, a connection that maintenance suspended shows Suspended — organization in maintenance, with a note that it resumes automatically when maintenance is turned off. A connection that a person suspended keeps the usual Suspended status and shows the reason that person gave.

Maintenance History

Below the switch, the Maintenance History table lists every change to the organization's maintenance mode:

Column	Description
Status	A color indicator: red for enabled, green for disabled.
Action	Whether maintenance mode was enabled or disabled.
Reason	The reason the administrator gave.
Timestamp	The date and time of the change.
User	The administrator who made the change.

If there are many records, use Previous and Next to move between pages.

How It Works

When maintenance mode is turned on for an organization:

1. The organization's settings are updated and the change is recorded in its settings history.
2. A maintenance event is published on the internal event bus.
3. Every engine replica stops starting new pipeline work for the organization and sends a cancellation to its running executions.
4. The connectors module suspends every connection of the organization and records the suspension as made by maintenance.

When maintenance mode is turned off, the engine starts accepting pipeline work for the organization again. The connectors module resumes only the connections that maintenance suspended.