Announcements
Our team noticed that the new canvas slows down significantly when editing a topic that has more than 20 nodes. Changing conditions or even text in a message node becomes glitchy and slow. We're using developer laptops so there is no shortage of computing power. Does anyone else experience the same issue?
Having the same issue. Tried recreating the bot from scratch, setting up a different environment, modifying small settings like Dark Mode and Co-Pilot, etc... nothing seems to resolve this issue and it's killing productivity.
I always advise when creating large topics to consider breaking them up into multiple sub-topics that you redirect to from your main topic. The sub-topics don't have to have triggers (unless it makes sense to let someone skip to that part) and in that way they can only be called directly from another topic. This could help you resolve part of the issue, and even in the original PVA, there were performance issues whenever you built out large topics, which could be resolved by this technique. I'd suggest looking at the first part of your topic that branches off and considering creating each of those branches as sub-topics.
I know it's probably not exactly what you're looking for, but could potentially help you out.
Cheers,Matt
We do split larger topics where it makes sense but sometimes splitting them up is not an option. It seems like an optimization issue too because the browser tab with PVA starts consuming large amounts of RAM when node count reaches double digits.
Hello @inzil2k @ThtFreaknGuy, this is Sumeet from the PVA engineering team.
Thank you for reaching out to us. We apologize for any inconvenience you may have experienced. We are aware of the issue you have shared with us, and our team is actively working on improving the performance of the canvas, especially when dealing with topics that have many nodes.
To address this problem, we have developed a beta version of the canvas that offers better performance. You can early access it by adding a specific URL query parameter(enablePerfCanvas=true) and refreshing the topic page. Applying this query parameter should help alleviate the issue.
Please keep in mind that we are currently in the process of propagating the performance updates. Soon, you can expect to have the improved canvas experience by default.
If you have any further questions or concerns, please don't hesitate to let us know.
Thanks, Sumeet
Thank you, @sumeet2010! Early testing with that performance canvas option turned on is allowing significantly better topic operation compared to before.
@MattJimison wrote:I always advise when creating large topics to consider breaking them up into multiple sub-topics that you redirect to from your main topic. The sub-topics don't have to have triggers (unless it makes sense to let someone skip to that part) and in that way they can only be called directly from another topic. This could help you resolve part of the issue, and even in the original PVA, there were performance issues whenever you built out large topics, which could be resolved by this technique. I'd suggest looking at the first part of your topic that branches off and considering creating each of those branches as sub-topics. I know it's probably not exactly what you're looking for, but could potentially help you out. Cheers,Matt
Love this recommendation from yours.This also aligns with the recently publish PVA Guidance content.
Let us know what you think: Topic authoring best practices - Power Virtual Agents | Microsoft Learn
Hi:
I had applied the Beta version by add the parameter but is still taking a long time to response. I am working on topics that had been converted from classic to the new version (facing issues with conversion as well but is on another chain discussion). Will you be able to provide a time estimate as to when the performance issue will be resolve?
Thanks,
Tak
Discussed offline with Tak on this issue. On applying the perf canvas flag, the performance has improved and user is able to access the canvas. Looks like earlier the flag was not applied correctly.Assuming this thread to be resolved.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Users!
Congratulations to our 2025 community superstars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Valantis 820
Vish WR 327
Haque 296
