Rebecca Lewis lays out the consequences of an existing bug:
If you use
SESSION_CONTEXT()in any query that can run with parallelism, you may be getting wrong results right now and not know it. This is not new. It has been a documented known issue since January 2022. It shipped unfixed in SQL Server 2019, 2022, and 2025 — and as of 2025 CU2 (February 12, 2026), it is still not resolved.This is easy to miss. It’s buried in the Known Issues section of CU release notes, and the symptoms — wrong results or dump files — do not obviously point back to SESSION_CONTEXT.
Read on to learn more about the issue, the current workaround, and how you can discern whether you are experiencing the issue today.