web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

Welcome to the Power Platform Communities
News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Copilot Studio / Delay in Copilot Topic...
Copilot Studio
Suggested Answer

Delay in Copilot Topic triggering in initial Message

(0) ShareShare
ReportReport
Posted on by CU26070739-0 2
Hi ,
 
I've developed the copilot chat bot and i'm facing the delay in copilot response in every session's initial message. It take minimum 30 secs to trigger a topic based on intent. Please refer the attached screenshot.
 
 
why there is 30-sec delay OR  how can i log that delay.
 
Any help would be greatly appreciated.
 
 
Thanks,
Nandhini.
 
Categories:
General topics
  • Suggested answer
    Vinoth Selvam Profile Picture
    Vinoth Selvam 1,597 Super User 2025 Season 1 on at
    Hi Nandhini,
     
    There are various factors related to the overall architecture, configuration, or integration between services.
     
    Use Azure Application Insights or Power Platform’s inbuilt telemetry to log message processing times at different stages.
    This will help pinpoint the stage where the delay is occurring.
     
    You can reduce the number of topics or intents for faster recognition, or switch to a pre-built, optimized model.
     
    Check if your Power Platform or Azure resources are sufficiently scaled to handle the load. If you notice the system slows down at peak times, you might need to increase the available capacity or add redundancy.
     
    If your bot connects to external systems (e.g., Dataverse, SharePoint), network latency might be contributing to the delay. Ensuring that your bot has quick and efficient access to these systems could help reduce the delay.
     
    Some bots have an "initial warm-up" period, especially after being idle for a while. This could cause the first interaction in a session to be slower than subsequent messages.
     
    Thanks.
  • CU26070739-0 Profile Picture
    CU26070739-0 2 on at
    Hi,
     
    The attached screenshot was  Azure Application Insights logs, where the bot received the message at 5:50:15 but the actual topic triggerred at 5:50:45, i dont know where to add the logs to track this delay.
    I've 500+ topics in this chat bot. This is not the consistent issue, but if the latency occurs, it is happening for the one whole day, then the next day it is  working fine and it repeats again.
    do we have any limitation for creating topics ? how to add logs to track this delay ?
     

    Any help would be greatly appreciated.
     
    Thanks,
    Nandhini
     
     

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.

Helpful resources

News and Announcements

Welcome to the Power Platform Communities

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the August Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Copilot Studio

#1
Mohsin Ali Profile Picture

Mohsin Ali 501

#2
M Bilal Khan Profile Picture

M Bilal Khan 222

#3
11manish Profile Picture

11manish 207 Super User 2026 Season 2

Last 30 days Overall leaderboard

Featured topics

Announcing the "Microsoft Copilot Studio ❤️ MCP" lab
Block PII/PCI in Copilot Studio agent user prompt

Product updates

Microsoft Power Platform Community release plans