# Troubleshooting automated executions

> Common issues with automated test set executions in Test Manager, including missing Orchestrator package publications and test case linking errors.

## Automated execution could not start since the package was not found on Orchestrator. Only test cases from packages which have been published to Orchestrator can be executed.

### Solution

You need to publish the Studio package to Orchestrator. This issue occurs when a test case is linked from Studio to Test Manager but the package is not yet published to Orchestrator.

## Test cases could not be executed since no executable versions could be found. Only test cases published with the latest package version to Orchestrator can be executed.

### Solution

This issue occurs when test cases in a test set are not published in the latest Studio package to Orchestrator. You might get the same error when there is no process/release found on Orchestrator for the Studio package.

## Automated execution could not start since no automated test cases could be found in this test set.

### Solution

You need to have at least one automated test case to use **Execute Automated**. For more information, see [Conditions](https://docs.uipath.com/test-manager/automation-cloud/latest/user-guide/executing-automated-tests#executing-automated-tests).

## There was an error executing the test set. Please try again.

### Solution

If execution of the test set fails for any reason other than the ones specified above, [get help from UiPath Support Services](https://customerportal.uipath.com/support/add-case).