diff --git a/docs/docs/migration/compatibility.mdx b/docs/docs/migration/compatibility.mdx index 8223bccebe2a..0e18e490058f 100644 --- a/docs/docs/migration/compatibility.mdx +++ b/docs/docs/migration/compatibility.mdx @@ -1,12 +1,12 @@ -import Admonition from '@theme/Admonition'; +import Admonition from "@theme/Admonition"; +import ZoomableImage from "/src/theme/ZoomableImage.js"; # Compatibility with Previous Versions - ## TLDR; - You'll need to add a few components to your flow to make it compatible with the new version of Langflow. -- Add a Runnable Executor, connect it to the last component (a Chain or an Agent) in your flow, and connect a Chat Input and a Chat Output to the Runnable Executor. This should work *most of the time*. +- Add a Runnable Executor, connect it to the last component (a Chain or an Agent) in your flow, and connect a Chat Input and a Chat Output to the Runnable Executor. This should work _most of the time_. - You might also need to update the Chain or Agent component to the latest version. - Most Components will work as they are, but you'll need to add an Input and an Output to your flow. - You can use the Runnable Executor to run a LangChain runnable (which is the output of many components before 1.0) @@ -22,23 +22,31 @@ We've tried to make it as easy as possible for you to adapt your existing flows ## How to Adapt Your Existing Flows - The steps to take are few but not always simple. Here's how you can adapt your existing flows to work seamlessly in the new version of Langflow: -

**Caution:**

-

While this should work most of the time, it might not work for all flows. You might need to update the Chain or Agent component to the latest version. Please let us know if you encounter any issues.

+

+ While this should work most of the time, it might not work for all flows. + You might need to update the Chain or Agent component to the latest version. + Please let us know if you encounter any issues. +

1. **Check if your flow ends with a Chain or Agent component**. - - If it does not, it *should* work as it is because it probably was not a chat flow. + - If it does not, it _should_ work as it is because it probably was not a chat flow. 2. **Add a Runnable Executor**. - - Add a Runnable Executor to the end of your flow. - - Connect the last component (a Chain or an Agent) in your flow to the Runnable Executor. + - Add a Runnable Executor to the end of your flow. + - Connect the last component (a Chain or an Agent) in your flow to the Runnable Executor. 3. **Add a Chat Input and a Chat Output**. - - Add a Chat Input and a Chat Output to your flow. - - Connect the Chat Input to the Runnable Executor. - - Connect the Chat Output to the Runnable Executor. - -{/* Add picture of the flow */} - + - Add a Chat Input and a Chat Output to your flow. + - Connect the Chat Input to the Runnable Executor. + - Connect the Chat Output to the Runnable Executor. + + diff --git a/docs/static/img/runnable-executor.png b/docs/static/img/runnable-executor.png new file mode 100644 index 000000000000..5db4b5134088 Binary files /dev/null and b/docs/static/img/runnable-executor.png differ