microsoft / microsoft/agent-framework
.NET: [Bug]: YAML validation is weak in some cases. Declarative.dll errors misleading or not self explainable
@peibekwe is already working on this.
Since Sep 3, 2026.
- Dominant language
- Python
- Stars
- 13.6k
- Forks
- 2.3k
- Avg merge
- 2d 45m
- Merged PRs (30d)
- 358
Description
Description
For the Declarative workflow documentation
YAML validation is weak in some cases. For example, I can set an invalid value on SendActivity instead of text (like prompt.test, not prompt.text) and only get runtime errors about missing variables instead of YAML validation errors.
If I set a variable such as Topic.ToolResponse in YAML, even when the namespace is wrong, validation does not complain. Fixing this problem need to be done carefully, cos we have undocumented behavior about namespaces Topic vs Local here
In general I can only infer what went wrong from limited runtime errors produced by the declarative.DLL that executes the YAML instructions.
Dll errors quite limited and do not provide useful info, so I need to guess what's going on.
If declarative.dll code debuggable, would be great to have instruction on how to do it/turn it on.
Code Sample
Error Messages / Stack Traces
Package Versions
Microsoft.Agents.AI.Workflows.Declarative
.NET Version
.NET 10.0.300
Additional Context
documentation related issue
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.