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

Community site session details

Session Id :
Copilot Studio - General
Suggested answer

Delay in Copilot Topic triggering in initial Message

(0) ShareShare
ReportReport
Posted on by 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:
I have the same question (0)
  • Suggested answer
    Vinoth Selvam Profile Picture
    1,565 Super User 2025 Season 2 on at
    Delay in Copilot Topic triggering in initial Message
    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
    2 on at
    Delay in Copilot Topic triggering in initial Message
    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

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Chiara Carbone – Community Spotlight

We are honored to recognize Chiara Carbone as our Community Spotlight for November…

Leaderboard > Copilot Studio

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 431 Super User 2025 Season 2

#2
Romain The Low-Code Bearded Bear Profile Picture

Romain The Low-Code... 311 Super User 2025 Season 2

#3
Arild Aarnes Profile Picture

Arild Aarnes 47

Last 30 days Overall leaderboard