## TL;DR

If sqlalchemy-oso session setup breaks right after a flask or werkzeug upgrade, pin werkzeug to 2.0.3 ahead of flask in your requirements file as an immediate workaround, then upgrade past the fixed releases.

## Steps

1. If sqlalchemy-oso session setup breaks right after a flask or werkzeug upgrade, pin werkzeug to 2.0.3 ahead of flask in your requirements file as an immediate workaround, then upgrade past the fixed releases. Dependency upgrades breaking Oso's session helpers is a known pattern, so check the werkzeug pin first before debugging your policy.

Expected: One user noted the underlying fix shipped in the Werkzeug 2.2.0 release.

## When to use

Use this skill when you run into "Pin werkzeug if Oso scoped sessions break on flask 2.1".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: 2.0.3, Werkzeug 2.2.0. If you are on something much newer or older, the details may have shifted.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
