Manual Test plans: inaccurate test run reports

**Symptom**: Some Progress Report data may display a higher number of "Not Run" tests than expected due to incomplete sync updates.

**Affected users**: Users who executed manual tests via API directly or through bulk marking between January 22, 2025, and February 26, 2025.

**Unaffected users**: Users who ran manual tests using web or desktop runners.

**Root cause**: A transient sync issue caused test results to be recorded but not consistently reflected in the Progress Report.

**Current Status**: Test runs after February 26, 2025, have synced correctly and appear accurately in the Progress Report. Engineering Team has been currently testing a hotfix which will fix the discrepancy from the backend. Once validated we will roll it out to impacted customers. We will update the ETA once we have more clarity.

**Recommendation**: Re-running the test will trigger the latest test result data to sync in the Progress report. This will also update the Test point execution date to the latest and cannot be reverted.

**Symptom**: Some Progress Report data may display a higher number of "Not Run" tests than expected due to incomplete sync updates.

**Affected users**: Users who executed manual tests via API directly or through bulk marking between January 22, 2025, and February 26, 2025.

**Unaffected users**: Users who ran manual tests using web or desktop runners.

**Root cause**: A transient sync issue caused test results to be recorded but not consistently reflected in the Progress Report.

**Current Status**: Test runs after February 26, 2025, have synced correctly and appear accurately in the Progress Report. The team is now working to synchronize test data from the impacted period.

**Recommendation**: Re-running the test will trigger the latest test result data to sync in the Progress report. This will also update the Test point execution date to the latest and cannot be reverted.