Replies: 1 comment
-
|
Thoughts here @lokitoth ? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello - maybe I'm missing the point, however I have tried to solve this myself for long enough so thought I'd engage the community.
I'm instantiating an agent from the workflow builder. When I run an instance of it - I would like to pass in some parameters.
The current recommended solution is to pass in a message (eg. CustomerId), and then have an initial executor which that populates some content based on the CustomerId. Put that content into the IWorkflowContext and then it's available for subsequent executors.
I think that the IWorkflowContext part makes sense. My question is around the initial parameters passed in.
I've tried a couple of ways (1) Passing in as a message, and then filtering out that message later on so it doesn't go back/forth from LLMs etc. (2) Using runOptions.AddtionalParameters["CustomerId"] and passing it in that way.
With option (2), those parameters never seem to make it into the IWorkflowContext. Some recommendation was to then retrieve them from the TraceContext, but this is also null.
Anyway, ultimately going round in circles - so feel like I'm missing a fundamental design prinicple. Any help appreciated!
Beta Was this translation helpful? Give feedback.
All reactions