microsoft / microsoft/agent-framework
.NET: [Bug]: Terminal Condition is not working in Magentic Orchestration
@peibekwe is already working on this.
Since Aug 12, 2026.
- Dominant language
- Python
- Stars
- 13.6k
- Forks
- 2.3k
- Avg merge
- 2d 45m
- Merged PRs (30d)
- 358
Description
### Description
I am testing Magentic Orchestration in .NET SDK. Here is my scenario -
1. As part of the user request, a local tool is calling Azure Resource Graph.
2. Azure Resource Graph is returning empty results because resource doesn't exist.
3. Magentic orchestration is considering this as failure even though I have mentioned this as valid scenario in the Magentic Manager instructions.
4. It keeps on replanning the orchestration. It is calling other unrelated agents as well as part of replanning.
5. Finally, request failed with as maximum number of rounds exceeded.
6. Sometimes, I received a response after a long delay. After reviewing the logs, I found that the request had been routed to multiple unrelated agents.
Looks like instructions in the Manager agent are not working for terminal state. How do I fix this?
### Code Sample
```markdown
```
### Error Messages / Stack Traces
```markdown
```
### Package Versions
1.14.0
### .NET Version
.NET 8.0
### Additional Context
_No response_
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.