[SDTEST][NOTICKET] Update troubleshooting of Test Optimization (#29394)

* Update troubleshooting of Test Optimization

* remove 'very'

* pr feedback

* pr feedback - remove possible mitigation

Author: TovRudyy

content/en/tests/troubleshooting/_index.md

@@ -175,6 +175,10 @@ This can be solved by using the `DD_TEST_SESSION_NAME` environment variable. Use
 
 This is also caused by an unstable test session fingerprint. See the [Session history, performance or code coverage tab only show a single execution](#session-history-performance-or-code-coverage-tab-only-show-a-single-execution) section for more information.
 
+## Flaky test management tags are missing or have an unexpected order in test events
+
+When retrying a flaky test multiple times within a short span of time (less than a second), test run events might contain unexpected `@test.is_flaky`, `@test.is_known_flaky`, or `@test.is_new_flaky` tags. This is a known limitation that occurs due to a race condition in the flaky test detection system. In some cases, test run events might be processed out of order, causing the tags to not follow the logical order of events.
+
 ## Further reading
 
 {{< partial name="whats-next/whats-next.html" >}}
@@ -194,4 +198,4 @@ This is also caused by an unstable test session fingerprint. See the [Session hi
 [13]: /tests/#parameterized-test-configurations
 [14]: /tests/#supported-features
 [15]: /agent/configuration/network/
-[16]: /tests/network/
+[16]: /tests/network/