Replies: 2 comments 1 reply
-
|
Hi @aleonsan, thanks for reaching out and supporting Agno! |
Beta Was this translation helpful? Give feedback.
-
|
Hi @aleonsan ! Thank you for the kind words. Sorry, but I think I am missing your concern here. The return type of That said, I do see the gap that |
Beta Was this translation helpful? Give feedback.







Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello all,
I've been using Workflows v2 since Agno v1 released it.
I had the following running workflow example with Agno v1 & workflows v2:
There, in the last step of the workflow,
gather_step_results, I could access directly to the structured output (StepResultmodel), with no transformation, usingStepInput.get_step_content, which code in Agno v1 was this.Now in Agno v2, this implementation has changed the output, and now it is not possible to access to the original structured output but a stringified version of it, see
StepInput.get_step_contentcode here.This change, obviously, has broken the workflow.
So,
.model_dump()in each of the last parallel steps, but this also produces an unnecesary overhead dumping/parsing. Is there any reason for this change inStepInput.get_step_content?Thanks for such amazing framework and for your support in advance.
Beta Was this translation helpful? Give feedback.
All reactions