Test Cloud admin guide

Planning and scheduling​

1. Depending on the services used by your tenant, the move may require multiple days to complete. Move date(s) are determined based on required version compatibility across regions.
2. A four-hour maintenance window is allocated for the region change. The average downtime is typically less than 30 minutes, but this can vary depending on tenant size. In rare cases, particularly for very large tenants, the move may take longer.
3. During the scheduled downtime window, the tenant is temporarily inaccessible.
4. Any running jobs are paused during the move and automatically resume after completion.
5. If you have scheduled or suspended robot jobs, temporarily disable them during the downtime window to help ensure a smooth migration.
6. Notify your cloud organization members in advance about the scheduled downtime window.

Scope and impact​

1. Changing a tenant's region does not affect the region of other tenants or the organization.
2. To move multiple tenants, submit and schedule region changes individually for each tenant.
3. To schedule a move for the entire organization, follow the Performing a cloud organization data move procedure.
4. For additional details about data behavior, see Organization and tenant services data.

Data considerations​

1. Only supported services are available for migration.
2. Services that are not supported must be recreated or manually reconfigured in the new region.
3. Some services may require additional configuration after migration.
4. Robot execution logs are retained for 30 days. Export logs in advance if you need to preserve them. For details, see Robot logs.
5. If your processes are integrated with UiPath Apps, you must update references after the move. See Replacing a process for guidance.
6. Insights can be moved to a new region. However, historical data backfilling is supported only within 30 days after moving Orchestrator. If Orchestrator is moved more than 30 days before Insights, Insights is moved without historical data, and only limited data is available after migration.

Migrate service data to the new region​

1. Go to Admin.

2. Select the tenant for which you want to change the region.

3. Go to Settings and find the Region section.

4. Select Change region. The Change tenant region wizard opens with three steps.

   1. Step 1 — Select region: From the Tenant target region dropdown, select the target region. The Service availability section updates to show each service and whether it is available in the selected target region. If some services are not available in the target region, a banner indicates this.
      Note:

      Region availability and data move support vary by service. If a service cannot be scheduled for migration, contact UiPath Support.

   2. Select Next.
   3. Step 2 — Select downtime window: Review the pre-assigned Downtime window (the 4-hour UTC time slot during which the migration will run) and the Compatibility window (the date range within which the migration can be scheduled). To use a different time slot, select one from the Or choose another downtime window (UTC) dropdown. You will receive an email notification when your migration is scheduled and when it completes.
   4. Select Next to continue.
   5. Step 3 — Confirm details: Review the summary showing the source and target regions, the downtime window, and the compatibility window. Confirm that the information is correct.
   6. Select Schedule to request the tenant service data move.

5. Once scheduled, the tenant's region status changes to Region change scheduled on the tenant's Settings page.

   

1. Navigate to Admin.
2. Select the tenant for which you want to cancel the scheduled move.
3. Go to Settings and find the Region section.
4. Select Region change scheduled to open the Scheduled data move panel.
5. Select Cancel request.
6. In the confirmation dialog, select Confirm.