---
title: "[Xray Cloud] I'm unable to import Tests"
canonical: "https://docs.getxray.app/space/ProductKB/46269430/%5BXray%20Cloud%5D%20I'm%20unable%20to%20import%20Tests"
format: markdown
---
> Macro (toc)


# Introduction


This article provides a guide to troubleshooting common issues and optimizing your testing workflow when importing tests using the Xray API or UI on both Jira Data Center and Jira Cloud.


---

# Common Issues & Potential Solutions:


## Software Version

Confirm whether you are using Xray Cloud or Xray Data Center and adapt to our documentation accordingly.

- Do you want to confirm your Xray Version? → [[Xray] How can I find my Xray version?](https://getxraydocs.atlassian.net/wiki/pages/viewpage.action?pageId=46269213)
- Looking for Xray Data Center article? → [[Xray DataCenter] I'm unable to import Tests](https://getxraydocs.atlassian.net/wiki/display/ProductKB/%5BXray+DataCenter%5D+I%27m+unable+to+import+Tests)


## Authentication Issues

Ensure you have the correct authentication credentials for the Xray API. This typically involves a **client_id** and **client_secret**.

- How-to → [[Xray Cloud] How to get API Keys](https://getxraydocs.atlassian.net/wiki/spaces/ProductKB/pages/46269250) & [[Xray Cloud] Can't generate API Keys (no user found)](https://getxraydocs.atlassian.net/wiki/pages/viewpage.action?pageId=46268831)
- Documentation → [Authentication - REST v2](https://getxraydocs.atlassian.net/wiki/display/XRAYCLOUD/Authentication+-+REST+v2)<span style="color: #ffffff">PUBLISHED</span>

<span style="color: #172b4d">You may also have authentication errors as described below:</span>

- **<span style="color: #172b4d">400 Bad Request </span>**<span style="color: #172b4d">- </span>
  - <span style="color: #172b4d">Possibly linked to a w</span><span style="color: #333333">rong request syntax. </span>
  - <span style="color: #333333">No import test job was created.</span>**<span style="color: #333333"> </span>**<span style="color: #333333">The content may be in the wrong format or a job might already be in progress.</span><span style="color: #333333"> </span>
  - <span style="color: #333333">Each user can only have one import job running at each given time. So if a job is running and the user tries to start another one, this will result in a 400 response. </span>
  - <span style="color: #333333">There is a maximum of 1000 tests that can be imported each time, if the input contains more tests than this, the request will also result in a 400 response.</span>
- **<span style="color: #172b4d">401 Unauthorized</span>**<span style="color: #172b4d"> - Possibly linked to your Xray license may no longer be valid</span>
- **500 INTERNAL SERVER ERROR** - <span style="color: #333333">An internal error occurred when authenticating the request.</span>
- <span style="color: #161719">There may be an error if your authentication token is revoked, in which case you should submit a new authentication.</span>


> ℹ️ **Readme**
> ℹ️ 
> ℹ️ The method you choose to import your test will determine the aspects you need to address.

## Importing using API

- **API Version Issues:**
  If you are encountering issues with the v1 API, consider switching to the v2 API.
  - Cloud v1 → [REST API v1](https://getxraydocs.atlassian.net/wiki/display/XRAYCLOUD/Version+1)
  - Cloud v2 → [REST API v2](https://getxraydocs.atlassian.net/wiki/display/XRAYCLOUD/Version+2)
- **Incorrect API Endpoint****: **
  Make sure you’re using the correct API endpoint for importing *Tests*. For Xray Cloud, the endpoint is different from the one used for Xray Data Center.
  - Cloud v1 → [Importing Tests - REST](https://getxraydocs.atlassian.net/wiki/display/XRAYCLOUD/Importing+Tests+-+REST)
  - Cloud v2 → [Importing Tests - REST v2](https://getxraydocs.atlassian.net/wiki/display/XRAYCLOUD/Importing+Tests+-+REST+v2)<span style="color: #ffffff">PUB</span>
- **Data Format Issues: **
  Ensure your *Tests *are in the correct format. For example, when importing using JUnit, make sure your tests are generating reports in the correct format.
  - Verify JUnit Structure → [Taking advantage of JUnit XML reports](https://getxraydocs.atlassian.net/wiki/display/XRAYCLOUD/Taking+advantage+of+JUnit+XML+reports)
  - When importing data via an API, format issues often arise in the request. For instance, when using the `curl` command, an incorrect number of quotation marks, or hidden characters can cause the request to fail.
  - Parameter-related issues are also frequent. If you provide the wrong Project key or Test Key, it can lead to problems during the import process.

## Importing using UI

- **Data Format Issues: **
  Ensure your *Tests *are in the correct format. For example, when importing using JUnit, make sure your tests are generating reports in the correct format.
  - Verify JUnit Structure → [Taking advantage of JUnit XML reports](https://getxraydocs.atlassian.net/wiki/display/XRAYCLOUD/Taking+advantage+of+JUnit+XML+reports)


> ⚠️ **Note:**
> ⚠️ 
> ⚠️ # Other Common Issues: 
> ⚠️ 
> ⚠️ **Error Messages:** Understand common error messages and their solutions. 
> ⚠️ 
> ⚠️ For example, a **404** error might indicate that you’re trying to import results to the wrong server. 
> ⚠️ 
> ⚠️ A “**No Project**” error might indicate an issue with the project key in your import file.
> ⚠️ 
> ⚠️ **Software Version Issues:** If you’re encountering issues after an Xray or Jira update, it could be a software bug. Check the Xray [support portal](https://jira.getxray.app/servicedesk/customer/portal/2) for known issues and updates.
> ⚠️ 
> ⚠️ 
> ⚠️ # Looking to learn more:
> ⚠️ 
> ⚠️ Check out this: [TTT: Examples using JUnit](https://getxraydocs.atlassian.net/wiki/display/XRAY/TTT%3A+Examples+using+JUnit)