Test step not found error during execution results submission

In qTest, a conflict occurs when a test step is removed from a test plan while an execution cycle is currently active. When the user attempts to submit the results for that specific cycle, the system fails to map the active execution data to the updated project schema.

This behavior suggests a synchronization gap between the client-side session cache and the centralized repository. While the system allows the deletion of steps in the plan editor, the results submission phase triggers a Test step not found error, preventing the completion of the logging for that execution run.

How does qTest handle the persistence of execution data when the underlying schema changes mid-session? Is there a mechanism to force the client-side cache to refresh metadata without terminating the active execution cycle?