Repository navigation
Run Flow component: any plans to move it out of beta? #16347
Replies: 3 comments
|
Answers to the three, with what the code actually says — one of them is a live bug worth its own issue. 1. Leaving beta. There is no published timeline. The class is 2. The So the distinction that decides your pattern:
The missing piece is that the parent contract for "a subflow produced no output" is undocumented, which is why this reads as a bug. Worth filing as one against 3. Versioning a subflow. Not supported and no plan: Practical upshot for reusable modules: keep the subflow's exposed input/output names stable and treat the whole thing as pre-1.0. If the beta flag matters to you organisationally, say so on the component — maintainer interest is the only thing that moves it. By the way, |
|
Worth one addition on the beta question, since it's the part that affects what you build against.
If the nesting behaviour you want is passing values back out, that's the part most likely to change — it's what the "beta" is actually gating. |
|
@igorleme-dev — the beta question has a concrete answer now: If that settles "can we depend on it", could you mark the comment above as the answer? It answers both halves of what you asked — timeline and safety. If you've since seen a release note or migration that changes the nesting contract, post it and I'll revise. |
Uh oh!
There was an error while loading. Please reload this page.
Hi! We're using Langflow 1.12.8 and would like to build reusable modules with the Run Flow component. It's still marked
beta = Trueinsrc/lfx/src/lfx/components/flow_controls/run_flow.py, in 1.12.8 and also in 1.13.1.A few questions:
None, and the parent fails with "Input data cannot be None". Is this expected, or is there a recommended pattern for routing inside a subflow?Thanks!
All reactions