From 37cfc003107ea800953be912f2eebfbf069c9587 Mon Sep 17 00:00:00 2001 From: Eugene Yurtsev Date: Wed, 22 May 2024 20:33:28 -0400 Subject: [PATCH] docs: concepts callbacks fix admonition (#22048) Correct the admonition text --- docs/docs/concepts.mdx | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/docs/docs/concepts.mdx b/docs/docs/concepts.mdx index d749d56c830..c1f79e5851b 100644 --- a/docs/docs/concepts.mdx +++ b/docs/docs/concepts.mdx @@ -535,10 +535,15 @@ of the object. If you're creating a custom chain or runnable, you need to remember to propagate request time callbacks to any child objects. -:::important -For code running python >=3.11, LangChain is able to automatically propagate -request time callbacks to child objects. This feature was added since -added as users forgetting to propagate callbacks was a common problem. +:::important Async in Python<=3.10 + +Any `RunnableLambda`, a `RunnableGenerator`, or `Tool` that invokes other runnables +and is running async in python<=3.10, will have to propagate callbacks to child +objects manually. This is because LangChain cannot automatically propagate +callbacks to child objects in this case. + +This is a common reason why you may fail to see events being emitted from custom +runnables or tools. ::: ## Techniques