JUnit results import is interrupted when sending multiple files, leaving part of the results unimported

When importing JUnit test results through the CI/CD integration (e.g. Jenkins) using multiple result files in a single import request, the process may be interrupted before all files are processed.

Expected behavior: All result files are imported successfully. Tests and test execution results are created or updated for every file provided.

Actual behavior: The import is interrupted partway through. The first file is processed correctly, but one or more of the remaining files fail silently or with an error, leaving their results unimported. The issue occurs intermittently and is more likely to happen when the test execution is created as part of the same import request (i.e. no pre-existing test execution key is provided, or the test execution was just created moments before).

Steps to Reproduce

1. Configure a Jenkins pipeline (or equivalent CI/CD tool) to publish JUnit results to Xray.

1. Ensure the job produces multiple JUnit XML result files.

1. Trigger the import with all files in a single request, without providing an existing test execution key (let Xray create one automatically).

1. Observe the imported results in Xray.

Expected Result

All test results from all files appear in the test execution.

Actual Result

Only a subset of the results is imported. The remaining files are skipped without producing a complete error report to the user.