# Expected Diagnosis: panic-in-recoverable-goroutine

This case should find the real recoverable-goroutine panic log and classify it
as an expected query timeout interruption. The correct answer should not dismiss
the alert as a fake alarm: the panic exists, but it is benign behavior from TiDB
interrupting a query that exceeded `max_execution_time`.

The expected evidence chain is:

- Loki contains a panic log around the alert window with `[executor:3024]` and
  `Query execution was interrupted, maximum statement execution time exceeded`.
- The panic is a timeout-interrupt pattern, not an abnormal TiDB bug.
- The impact is limited to the timed-out query; TiDB recovers the goroutine.
- No TiDB fix is needed for the panic itself. Optional follow-up is to inspect
  the timed-out query and tune query performance or timeout settings if needed.