You’re offline. This is a read only version of the page.
I am experiencing an issue with the topic cancellation functionality in our copilot studio deployed on Microsoft Teams. We have implemented a flow that involves 4-5 topics to loop over a list of PDFs, generate summaries using generative answers, and write the responses to an Excel sheet.
Current Implementation:
Expected Behavior: The virtual agent should immediately cancel the ongoing flow and stop execution upon receiving the cancellation command.
Current Behavior: The virtual agent does not cancel the flow immediately. It only shows the cancellation message after all topics have been executed.
Steps Taken:
Questions:
Any insights or suggestions would be greatly appreciated. Thank you!
Set Cancellation Topic as Highest Priority: Ensure that the cancellation topic has the highest priority in Copilot Studio, so it interrupts other topics as soon as the cancellation trigger is detected. This can help the bot respond to cancellation requests immediately, even in the middle of ongoing processes.
Use Interruption Handlers: Configure an interruption handler in Copilot Studio to actively listen for the cancellation command throughout the process. Set up cancellation checks within each topic, especially before initiating each new PDF summary or Excel write operation, allowing the bot to stop more promptly.
Divide Long Processes into Smaller Segments: Break down the PDF summarization and Excel update processes into smaller segments or batches. This way, the bot frequently pauses to check for cancellation commands, ensuring it doesn’t get “stuck” in a long-running process without listening for the cancellation input.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
Share
Report
All responses (
Answers (
1,278
