Jenkins to qTest result mapping precedence for parallel build executions

When Jenkins publishes automated test results to qTest Manager via the integration plugin, the system maps JUnit XML outputs to specific test cases based on identifiers. A challenge arises when multiple Jenkins agents or parallel stages execute the same logical test case simultaneously or in rapid succession.

The integration boundary defines how qTest handles overlapping results for a single test case within the same build cycle. If one agent reports a PASS and another concurrent agent reports a FAIL for the same identifier, the system's behavior for determining the final status of the test run is not clear.

Does qTest create distinct test runs for each parallel Jenkins agent, or does it consolidate results into a single run? In the event of conflicting statuses, does the integration follow a 'last-build-wins' logic, or is there environment-specific precedence applied?