# Licensing and integration troubleshooting

> Diagnose and fix licensing, runtime, and integration issues in Test Cloud — covers runtime errors, pending test cases, and Jira Server connectivity.

## App Testing runtime error when scheduling test execution

**Symptom:** An App Testing runtime error appears when scheduling or executing test cases.

**Cause:** The app test robot lacks an App Testing Runtime license, or the runtime type configured in Test Manager does not match the allocated license.

**Resolution:**

1. In Admin settings, verify that at least one **app test robot** has an **App Testing Runtime** license allocated.
2. Assign the App Testing Runtime license to the machine template in use.
3. Confirm the user has the **Automation Developer** or **Test Manager** role.
4. In Test Manager, open the **Configure Automation** panel and verify the selected runtime type matches the allocated license. For Test Cloud, **App Testing** is commonly used.

The default Test Cloud trial includes only **App Test Developer** licenses. To request additional Pro user licenses or services, contact your UiPath account representative.

## Test cases stuck in Pending state with App Testing license only

**Symptom:** Test cases remain in Pending state when the app test robot has only App Testing licenses.

**Cause:** The app test robot may be missing a required license type, or the Studio project configuration does not match the expected runtime requirements.

**Resolution:**

1. If the issue persists, try adding a **Testing** license to the app test robot in addition to the existing App Testing license.
2. Verify the Studio project type is set to **Test project**.
3. Check for package version requirements and update the test project dependencies if needed.

## Test Manager shows 0 App Testing runtimes despite a configured machine template

**Symptom:** A machine template has App Testing runtimes configured, but Test Manager shows 0 available App Testing runtimes.

**Resolution:**

1. Open Orchestrator and verify the App Testing runtimes are correctly allocated and visible for the machine template in use.
2. If runtimes appear correctly in Orchestrator but Test Manager still shows 0, contact UiPath Technical Support.

## Error: HostMachineName and ServiceUsername must both be provided or both be empty

**Symptom:** Saving a test set configuration fails with a validation error when the app test robot is installed in Service Mode.

**Cause:** In Service Mode, `serviceUsername` is empty. The API rejects payloads where only one of the two required fields is populated.

**Resolution:** This is a known environment-specific issue with no current workaround. Open a support ticket and attach HTTP Archive (HAR) logs for further investigation.

## Orchestrator becomes inaccessible after trial expiration

**Symptom:** After the 60-day trial expires, access to Orchestrator is lost.

**Resolution:**

1. Contact your UiPath account representative or the licensing team to request a trial extension.
2. Once the extension is confirmed, access is restored. If access remains unavailable after the extension is confirmed, contact UiPath Technical Support.

## Jira Server integration — connection timeout to cloud.uipath.com

**Symptom:** After configuring a Jira Server connection in Test Manager, saving the configuration fails with: `Connect to cloud.uipath.com:443 failed: Connect timed out`.

For information on configuring the Jira integration in Test Manager, see [Atlassian Jira](https://docs.uipath.com/test-manager/automation-cloud/latest/user-guide/connecting-a-jira-project).

**Cause:** The Jira Server instance cannot reach `cloud.uipath.com` on outbound port 443.

**Resolution:**

1. In your firewall configuration, add `cloud.uipath.com` to the allowlist for outbound traffic on port 443.
2. Confirm the allowlist rule is active in your firewall configuration.
3. Retry the Jira Server connection in Test Manager.