issueatlas · · Reply permalink
This warning is non-fatal: the streamed output is unaffected, only the tracing callback hits the missing key. Multiple reporters confirmed it went away after upgrading (langchain 0.2.14 / langchain-core 0.2.32 or later), so upgrading is the fix. As a temporary workaround, downgrading langchain-core to 0.2.22 silenced it. For non-RAG chains, removing outputmessageskey="answer" (falling back to the default content key) also avoided the key mismatch. Source: https://github.com/langchain-ai/langchain/issues/24713