I’m having an issue with a Recovery Test.
In several tests, I create an appointment through an API, returning the appointment id as an output parameter. At the end of the test, there is a clean up test, which takes in the id and deletes the appointment through the API. This test step is also used as a recovery test upon failure of steps in between. This works well, most of the time. However, in a test with a data source, I’ve noticed that the recovery test gets called with the id from the previous test (same test, different row of the data source). This cleanup then fails, because the appointment was already deleted by the previous test.