Skip to main content
Version: 3.9

Maintenance Mode in R-COM Gateway

Maintenance Mode in R-COM Gateway provides controlled system isolation during upgrades, configuration changes, migrations, or emergency fixes without forcing a complete service blackout.

Unlike traditional maintenance modes that block all access and activity, R-COM Gateway supports Selective Access–Based Maintenance Mode. This allows administrators to restrict user access while optionally keeping core event processing active, enabling final validations and controlled operations during maintenance windows.

What Maintenance Mode Does​

When Maintenance Mode is enabled:

  • Login access is blocked for all users except explicitly allowed roles and groups
  • A system-wide maintenance banner is displayed in the UI
  • Gateway behavior can be precisely controlled:
    • Either continue processing events
    • Or fully suspend all event processing and automation

This approach ensures operational safety without sacrificing observability or controlled access.

Key Capabilities​

Selective User Access​

You can allow specific users to continue accessing the Gateway while maintenance mode is active. Access is granted to users who match at least one configured bypass role or Access Group:

  • A selected Maintenance Bypass Role
  • A selected Maintenance Bypass Access Group

At least one bypass role or group must be selected before Maintenance Mode can be enabled. All other users are prevented from accessing the Gateway.

Controlled Event Processing​

Maintenance Mode allows explicit control over gateway operations:

  • Event Rules Enabled

    • Core event ingestion and workflows continue running
    • Useful for validating fixes, monitoring live data, or controlled testing

  • Event Rules Disabled

    • All real-time processing and automated workflows are stopped
    • Gateway operates in a fully paused state

This ensures maintenance actions do not unintentionally trigger workflows or external integrations.

System-Wide Maintenance Messaging​

A configurable maintenance message is displayed:

  • On the login screen
  • In the gateway header for logged-in bypass users

This clearly communicates the system state and prevents user confusion.

Enabling Maintenance Mode​

warning

Before enabling Maintenance Mode, ensure:​

  • Maintenance Mode is enabled for the gateway instance
  • Your user account has sufficient permissions to manage client settings

Configuration Steps​

  1. Navigate to Administration > Maintenance > Maintenance Mode.
  2. Select Edit.
Enable Maintenance Mode

Enable Maintenance Mode

  1. Configure the following options:

    • Maintenance Mode: Enable this toggle to activate maintenance mode gateway-wide.
    • Reject Sync HTTP Requests (REJECT_SYNC_REQUESTS_ENABLED): Return HTTP 503 for synchronous HTTP events during maintenance. Rejected events are not added to the event queue.
    • Restrict Event Rules: Pause Event Rule processing during maintenance. When disabled, event processing continues normally.
    • Maintenance Mode Message: Custom message shown to users during maintenance.
    • Roles that can access the system during maintenance: Roles allowed to bypass maintenance restrictions.
    • Groups that can access the system during maintenance: Access Groups allowed to bypass maintenance restrictions.
warning

A user needs a selected bypass role or Access Group to retain access.

warning

Enabling maintenance mode on one client activates it for all clients in the same R-COM Gateway instance

  1. Select Update.

Behavior After Activation​

  • Maintenance Mode remains active until it is manually disabled
  • Only bypass-authorized users can log in
  • All other login attempts are blocked
  • Gateway behavior strictly follows the selected Event Rules setting
info

There is no automatic timeout or rollback. This is intentional, maintenance mode is an explicit operational state and must be exited deliberately.

When to Use Maintenance Mode​

  • Platform upgrades or configuration changes
  • Workflow or integration refactoring
  • Emergency patches or hotfixes
  • Data migrations or schema changes
  • Controlled validation in production environments

Related Articles