Repository navigation
Replies: 1 comment
|
Turned this into an issue to better track it. Please follow along here: #4639. |
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.
I think there is likely something very simple that I am missing in workflow/executor settings, but I cannot find it. I have an adapted version of WorkflowAgentsInWorkflowsSample example. I am grabbing all of the events, and my output is shown below. Things to notice:
ExecutorInvokedEventevents with the output from the prior stages.ExecutorCompletedEventevents have no data. (TheDatafields arenull, but showing up here as empty strings.)QUESTION: Why are the
ExecutorCompletedEvent.Datafields empty? Is this expected for agents? Is there a setting that controls this?I was anticipating that I would get
ExecutorCompletedEventevents with the complete data for all of theAgentResponseUpdateEventevents. (I have seen cases where the data is streamed across multipleAgentResponseUpdateEventevents, so this would be very useful.) This would match the correspondingExecutorInvokedEventevent, however, I have also noticed that with agents, we get two pairs of invoked/completed events.ExecutorInvokedEventevent with the input.ExecutorCompletedEventwith no data.ExecutorInvokedEventevent with "Microsoft.Agents.AI.Workflows.TurnToken" as its data.ExecutorCompletedEventwith no data.All reactions