duplicate test case is getting created in a fresh created test cycle after the test execution

Hi Support Team,

We're experiencing an issue after migrating to Zephyr Scale Cloud and would like to understand whether this is expected behavior or if we're missing something.

Steps to reproduce

1. Create a new test cycle manually using the Zephyr Scale UI.
2. Add an existing test case from the project to the test cycle.
3. The test case appears in the cycle with a Not Executed status.
4. Execute the test externally and update the result using the POST /v2/testexecutions API.

Request:

curl -H 'Authorization: Bearer <token>' \ -H 'Content-Type: application/json' \ -d '{ "projectKey": "SI", "testCaseKey": "SI-T20217", "testCycleKey": "SI-R3669", "statusName": "Pass", "comment": "", "assignedToId": "siqauto", "executedById": "qaautobot", "executionTime": 32, "actualEndDate": "2026-06-30T21:29:32Z", "testScriptResults": [], "environmentName": "QAS" }' \ https://api.zephyrscale.smartbear.com/v2/testexecutions

Actual behavior

Instead of updating the existing Not Executed test case in the cycle, the API creates a second entry for the same test case.

The test cycle now contains:

SI-T20217 Not Executed SI-T20217 Pass

Expected behavior

We expect the existing Not Executed test case in the cycle to be updated with the execution result, so that the cycle contains a single entry:

SI-T20217 Pass

We have reproduced this behavior consistently with newly created test cycles and manually added test cases.

Could you please confirm whether this is the expected behavior of the POST /v2/testexecutions API, or let us know if there is something we're doing incorrectly?

Thank you.