Error when reactivating a tenant

Symptoms

In the IBM RPA Control Center, when you try to reactivate a deactivated tenant, you get the following error: An error occurred. Try again later.

Causes

This occurs because of a known issue with the integration between the UI and the API. The UI sends an HTTP request to an endpoint that does not exist.

Affected Offerings

IBM RPA on premises, IBM RPA on Red Hat® OpenShift® Container Platform and IBM RPA SaaS.

Resolving this issue

To reactivate the tenant, you need to manually program an HTTP request to the correct endpoint.

Requirements:

  • You need Platform administrator privileges on the tenant to resolve this problem.
  • Your user needs to have access to the deactivated tenant. In other words, your user was previously added by someone to the tenant before its deactivation.

Editing and resending the HTTP request on Mozilla Firefox

On the Mozilla Firefox browser, you can edit and resend an HTTP request using the Developer Tools on Mozilla Firefox.

  1. Open the Developer Tools.
  2. Navigate to the Network tab.
  3. Optional: Clear the network logs.
  4. Navigate to the IBM RPA Control Center and click the vertical ellipsis button &vellip > Reactivate. You get an error with the network logs record from the failed HTTP request highlighted.
  5. Identify the failed HTTP request, right-click it and select Edit and resend. A new pane on the Developer Tools opens.
  6. Edit the last path in the URL, replacing reactivate to resume.
  7. Click Send.

If you receive the 200 status code, you have successfully reactivated the tenant.

Reactivating the tenant by using the API

You can send requests to the API to reactivate the tenant. You need to know what the API URl is on your IBM RPA environment. Follow these steps to proceed:

  1. Getting the API URL.
  2. Getting the deactivated tenant ID and the first-tenant ID.
  3. Authenticating to the first tenant.
  4. Reactivating the tenant.

If you receive the 200 status code, you have successfully reactivated the tenant.

Getting the API URL

If you are using IBM RPA on premises or IBM RPA on Red Hat® OpenShift® Container Platform you set the API URL endpoint during installation. Refer to the infrastructure administrator of your organization if you need guidance.

If you are using IBM RPA SaaS, you can get the API URL from the region your tenant is assigned to by replacing app on the IBM RPA Control Center URL with api. For example, us1api.rpa.ibm.com.

Getting the deactivated tenant ID and the first-tenant ID

Use the following HTTP request:

GET /v2.0/account/tenant?UserName={username}
Host: {api_url}
Accept: application/json, text/plain, */*
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US,en;q=0.9
User-Agent: {user_agent}

The response is a list of all tenants your username can access. Get the id from the tenant that you want to reactivate and the id of the first tenant created on the server. The tenant you want to reactivate maintains same name as before deactivation plus the date of when it went to deactivated state. For example, MyTenant-20220623-102534.

Authenticating to the first-tenant

Use the endpoint to Get a JSON Web Token (JWT). See the IBM RPA's APIs reference for details. You must authenticate to the first tenant created on the IBM RPA server. You must get the access_token value from the response.

Reactivating the tenant

The function to reactivate the tenant is called resume. Use the following HTTP request to reactivate the tenant:

PATCH /v2.0/tenant/{deactivated_tenant_id}/resume
Host: {api_url}
Accept: application/json, text/plain, */*
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US,en;q=0.9
User-Agent: {user_agent}
Authorization: Bearer {access_token}