Guides
Guides
Breadcrumbs

Working with multi-region Environments

This page applies to US1 customers whose traffic runs in both US1 East and US1 West. It explains how to keep your applications the same in both regions.

Applications in US1 East and US1 West are not synchronized automatically

If your traffic runs in both US1 East and US1 West, each region runs its own copy of your application. Changes you publish in US1 East don't reach US1 West automatically. Apply every change in both regions, and release the US1 West update together with your US1 East release.

Releasing changes in both regions

To keep both regions in sync, follow these guidelines:

  1. Build and test on US1 East (us1-m.ocp.ai).

  2. Export the production application from US1 East.

What the export includes. When you export an application, the file it creates includes all of its miniApps, flows (canvases) and the NLU model. When you import that file into US1 West, Environments Manager creates or updates all of those miniApps and canvases.

  1. Import it on US1 West (us1-w-m.ocp.ai), into the same production OCP groups, keeping the same application name.

You can use the same login credentials on US1 West as on US1 East.

NLU on import. When you import an application into a different environment, do not select "Include imported NLU references". Environments Manager will create a new NLU model in the target environment.

Masked collection variables.
Masked collection variables are not copied by export and import. Whoever has access needs to update them manually in US1 West after each import.

  1. Deploy the application on US1 East & West production group.

  2. Promote the application on US1 East & West production group.

  3. Test

    1. Run an interoperability test using one virtual number from each of the East, West, and East and West ranges, end-to-end across both instances,

    2. or, simpler, use the multi-region pseudo number for testing and make sure that calls land on both East and West to complete the testing.

Copy between matching groups: Dev to Dev, UAT to UAT, and Prod to Prod. For the steps, see Manage Applications and Application Tags and Deploying Dialog Application.

Include time in your release plan to test in US1 West.

Always import the US1 East export into US1 West. Don't rebuild the application manually, because the application IDs must match in both regions.

Do not rename the application to avoid mismatch between environments. Application names must match in both regions.