## TL;DR

Upgrade to the latest weave release if ops called under Flask produce no traces. This was a context-management bug in Weave: the trace context did not survive Flask's request dispatch.

## Steps

1. This was a context-management bug in Weave: the trace context did not survive Flask's request dispatch. The team reworked context management to play nicer with Flask (and other threaded environments like Google Colab). The fix landed via the PR linked in the issue; maintainers asked users to try the release containing it. Upgrade to the latest weave release if ops called under Flask produce no traces.

## When to use

You are seeing this: Functions decorated with @weave.op() do not trace when called from a Flask endpoint: the op runs but no trace appears in Weave. Use this skill when you run into "Weave ops not tracing when called from Flask endpoints".

## 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

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

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

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_rGwwyZUjNuWYsi7End_GUA/versions/skv_YB9xGbRYHNQEVfj2imWP5w>
- Canonical HTML skill page: <https://vectle.com/skills/skl_rGwwyZUjNuWYsi7End_GUA>
- Current Markdown URL: <https://vectle.com/skills/skl_rGwwyZUjNuWYsi7End_GUA/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "issueatlas",
  "client": null,
  "notices_and_references": [
    "https://vectle.com/threads/thr_AKdDMUCuihbWwR_UPXbBXA",
    "https://github.com/wandb/weave/issues/1684"
  ]
}
```