Jacob Alber 4940d0ef36 fix: Subworkflows do not work well with HostAsAgent (#3240) ...

Subworkflows run into issues with Checkpointing and the Chat Protocol:

* The concurrency rework made subtle changes in behaviour that introduced a hang when using subworkflows with ChatProtocol and streaming execution.
* The ResetAsync() implementation in WorkflowHostExecutor was improperly resetting the joinContext - this was happening on restore checkpoint _after_ the join context was attached when
* Subworkflows cannot be used as the start node when hosted AsAgent due to inability to treat Catch-All as a Chat Protocol
* Subworkflow ownership issue when used in non-concurrent mode after finishing a run

Also fixes:
* When ChatMessages are output by executors that are not agents, there is no corresponding AgentResponseUpdate/AgentResponse event

Breaking Changes
* [BREAKING CHANGE] It is possible to provide the wrong RunId when resuming from CheckpointInfo (even though the data already exists on CheckpointInfo)

4940d0ef36 · 2026-01-22 16:01:47 +00:00

History

..

CheckpointAndRehydrate.csproj

.NET: Upgrade to .NET 10 (#2128)

2025-11-22 04:14:15 +00:00

Program.cs

fix: Subworkflows do not work well with HostAsAgent (#3240)

2026-01-22 16:01:47 +00:00

WorkflowFactory.cs

samples: WorkflowHelper => WorkflowFactory (#1640)

2025-10-23 04:34:26 +00:00