I am using Magentic orchestration to run a sequence of queries. The first query executes and completes successfully, but once it finishes, the orchestration does not trigger or continue to the next query. The workflow stops after the initial query completion with an error. New query can only be passed when a new session is created.
- Configure Magentic orchestration with multiple queries in sequence
- Start the orchestration
- Observe that the first task runs and completes
- Notice that the next query produces a runtime error.
After the first query completes, the orchestration should automatically proceed to and execute the next query in the defined workflow. In other orchestrations, multi turn conversation takes place.
The orchestration stops once the first query is completed. No subsequent query is triggered.
Is there a required configuration, state transition, or explicit trigger to ensure that subsequent queries run after one query completes?
What is the recommended approach to chain or advance queries correctly in Magentic orchestration for multi turn conversation?
I am using Magentic orchestration to run a sequence of queries. The first query executes and completes successfully, but once it finishes, the orchestration does not trigger or continue to the next query. The workflow stops after the initial query completion with an error. New query can only be passed when a new session is created.
After the first query completes, the orchestration should automatically proceed to and execute the next query in the defined workflow. In other orchestrations, multi turn conversation takes place.
The orchestration stops once the first query is completed. No subsequent query is triggered.
Is there a required configuration, state transition, or explicit trigger to ensure that subsequent queries run after one query completes?
What is the recommended approach to chain or advance queries correctly in Magentic orchestration for multi turn conversation?