Skip to main content
Feedback

Enabling and Configuring MCR Environments

To start using MCR environments, a tenant Administrator must first enable them in your tenant. Once the feature is enabled, you have both MCR nodes and environments turned on for your tenant.

note

You must be a tenant Administrator to enable environments for a tenant.

By default, each tenant includes Development, Test, and Production environments within the cloud, with the option to add more environments as needed. You can associate different MCR (Multi-Cloud Runtime) nodes with individual deployment environments. This means that when a release is deployed—for example, to the Test environment—the system promotes the release only to the MCR node configured for that environment. This configuration enables greater flexibility in managing deployments across various environments, including development, test, and production.

note

You must have at least one MCR node configured for your tenant.

To enable environments in a tenant:

  1. Select Tenant from the top Settings menu to open the Tenant page.

  2. In the Environments section, select​​ the Enable Environments toggle. The selection enables the tenant to use the Environments feature.

  3. Select Environments from the top Settings menu to choose the environment you want to configure (for example, Test or Production).

  4. Select the associated MCR nodes.

    • In the environment settings page, locate the Local Runtimes selector. The selector lists all available MCR nodes for your tenant.
    • Select the node(s) you want to associate with this environment.
    tip

    You can assign different nodes to different environments based on capacity, region, or testing needs.

Suppose you already have an MCR node set up and choose to enable environments. In that case, the setting will automatically sync to the MCR node during its subsequent communication with the cloud, turning on environments within the MCR node.

important

Once the environments setting is enabled, published versions of the flows will no longer be accessible on the MCR node. To ensure that your flows are available in production, you must create a new release that includes the necessary flows and push this release through all designated environments. Alternatively, you can start a new MCR node on a blank database or tenant.