Skip to content

.NET: [Bug]: Terminal Condition is not working in Magentic Orchestration #7595

Description

@assing

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

Error Messages / Stack Traces

Package Versions

1.14.0

.NET Version

.NET 8.0

Additional Context

No response

Metadata

Metadata

Labels

.NETUsage: [Issues, PRs], Target: .NetorchestrationUsage: [Issues, PRs], Target: multi-agent orchestration (high-level patterns)

Type

Projects

Status
No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions