Langchain Integration adds redundant chain callbacks

[mshavliuk]

How do you use Sentry?

Sentry Saas (sentry.io)

Version

2.32.0

Steps to Reproduce

When I configure the SentryLangchainCallback instance for invoke call I expect Sentry langchain integration not to create another instance of the same callback.

To reproduce the issue run code with breakpoints inside _wrap_configure:

import os

import sentry_sdk
from langchain_aws import ChatBedrockConverse
from langchain_core.runnables import RunnableConfig, RunnableLambda
from sentry_sdk.integrations.langchain import LangchainIntegration, SentryLangchainCallback

sentry_sdk.init(
    dsn=os.environ["SENTRY_DSN"],
    environment="localhost",
    traces_sample_rate=1.0,
    integrations=[LangchainIntegration()],
)

llm = ChatBedrockConverse(
    region_name="eu-west-1",
    aws_access_key_id=os.environ["AWS_ACCESS_KEY_ID"],
    aws_secret_access_key=os.environ["AWS_SECRET_ACCESS_KEY"],
    model="eu.amazon.nova-lite-v1:0",
    # intentionally invalid config to trigger error
    additional_model_request_fields={"inferenceConfig": {"topK": 0}},
)
parser = RunnableLambda(lambda x: x)

config = RunnableConfig(callbacks=[SentryLangchainCallback(max_span_map_size=100, include_prompts=True)])

chain = llm | parser
chain.invoke('hello', config)

Installed dependencies:

annotated-types==0.7.0
anyio==4.9.0
boto3==1.38.22
botocore==1.38.22
certifi==2025.4.26
charset-normalizer==3.4.2
h11==0.16.0
httpcore==1.0.9
httpx==0.28.1
idna==3.10
jmespath==1.0.1
jsonpatch==1.33
jsonpointer==3.0.0
langchain==0.3.25
langchain-aws==0.2.18
langchain-core==0.3.55
langchain-text-splitters==0.3.8
langsmith==0.3.42
numpy==2.2.6
orjson==3.10.18
packaging==24.2
pydantic==2.11.5
pydantic_core==2.33.2
python-dateutil==2.9.0.post0
PyYAML==6.0.2
requests==2.32.3
requests-toolbelt==1.0.0
s3transfer==0.13.0
sentry-sdk==2.32.0
six==1.17.0
sniffio==1.3.1
SQLAlchemy==2.0.41
tenacity==9.1.2
typing-inspection==0.4.1
typing_extensions==4.13.2
urllib3==2.4.0
zstandard==0.23.0

Expected Result

I expect Sentry not to create another instance of the same callback handler.

Actual Result

Sentry integration creates a new instance of SentryLangchainCallback and attaches it to the chain, so every even processed twice (once by the manually created and configured callback handler and second time by another callback handler with default parameters).

Having multiple callbacks sending errors to Sentry leads to more problems down the line.

[mshavliuk]

This is not a duplicate of #4443 which I reported previously. The difference is that previously all inherited callbacks were ignored and led to redundant callback creation. Now the issue reproduces only for RunnableSequence which passes CallbackManager instance as inheritable_callbacks parameter to the _wrap_configure method. The _wrap_configure expects it to be a list, whereas Callbacks could also be a CallbackManager as evident by this langchain type definition

[szokeasaurusrex]

I believe #4486 (which I already opened last week) will fix this issue