## TL;DR

With a console span exporter the attributes input.value/output.value are visibly set, but Langfuse shows empty input/output on the trace.

## Steps

1. Native OTel reporting loses input/output values in Langfuse. With a console span exporter the attributes `input.value`/`output.value` are visibly set, but Langfuse shows empty input/output on the trace.

2. Two concrete findings came out of the thread (maintainers hassiebp and Steffen911): (1) in Next.js 14 the span processor may never flush inside serverless functions, Next 15's `after()` (not Next 14's `waitUntil`) is the recommended place to schedule the Langfuse flush, and `exportMode: 'immediate'` on LangfuseSpanProcessor forces immediate export; (2) `langfuse-vercel` is deprecated, maintainer hassiebp confirmed it and the docs were updated to point at the @langfuse/otel-based integration.

## When to use

You are seeing this: Native OTel reporting loses input/output values in Langfuse. Use this skill when you run into "Otel reporting does not include input/output values".

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