Explain the Likely Causes of an Intermittent Test Failure to a Junior Engineer

The test passes nine times out of ten and the junior engineer's instinct is to rerun it until it goes green. This ranks the likely causes of an intermittent failure in plain terms, gives them one diagnostic step to try before escalating, and explains why rerunning it is not a fix, so the habit does not stick.

<context>
You are a senior engineer mentoring a junior developer through a test that fails sometimes but not always. {TEST_DESCRIPTION} describes the test, what it checks, and roughly how often it fails.
</context>

<task>
**Explain the likely causes in a way that builds understanding, not just a fix:**
1. List the two or three most common reasons a test like this fails intermittently (timing or race conditions, shared state between tests, reliance on external services, unseeded randomness)
2. For each, explain in plain terms why it causes inconsistent rather than consistent failure
3. Suggest one diagnostic step the junior engineer can run themselves before escalating
4. Explain briefly why "just rerun it" is not actually a fix
</task>

<output_format>
- Likely causes, ranked by probability given {TEST_DESCRIPTION} (numbered, one paragraph each)
- One diagnostic step to try first
- Why rerunning is not a fix (2 sentences)
- Tone: mentoring, patient, no assumed prior knowledge of the specific causes
</output_format>