Copilot Studio

Why does Prompt not work in Teams and does great in Copilot Studio Test

(1) Share

Report

Posted on by vsivakumar

Categories:

Building Copilot Studio chatbots in Microsoft Teams

I have the same question (0)

All responses (7)

Answers (0)

S-Venkadesh 1,214 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Hi @vsivakumar,

Could you please explain what your Agent does — including its instructions, topics, and any cloud flow logic involved?

The likely causes of this issue could be:

The flow is taking longer to respond — note that timeout values differ between the published and test (unpublished) versions.

The message data size might be too large.

I hope this information helps! If it does, please consider giving a 👍.
Best regards,
S-Venkadesh

Was this reply helpful? Yes No
vsivakumar 25 on at

Like (0)

Report
Copy link

Link copied!

It is a SOW writer agent that takes input like customer name, Sharepoint link, sample template and estimates in text in a topic. Then this topic calls a power automate agent workflow that called a prompt flow which has additional instructions and all the inputs entered by user. The SOW text generates and emails in the agent flow and returns too back to the topic and closes the conversation after taking user feedback. All this happens nicely in copilot studio test. However the same fails in Teams. We need this fix urgently for a demo later today.

Sorry, something unexpected happened. We’re looking into it. Error code: SystemError. Conversation ID: a:14R89YWKCEAyx8jgUhnbTQbTXD6G8r5gAqQPOiHROgn4ss5QxsrZ3eUJKLxiNB0xpidUEe6lC3NX7Kr-lEM1_50yOfd4SDsSwUscfoyw39788yQBe1q28t2tZtOtQ5ubT. Time (UTC): 11/11/2025 1:39:39 PM.

Was this reply helpful? Yes No
S-Venkadesh 1,214 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Hi @vsivakumar,

The details provided are still insufficient to identify the root cause.
Based on your workflow description, a likely cause is that Power Automate is taking too long to respond.
To troubleshoot:

Check how long your Power Automate flow takes to execute.

For testing, temporarily remove or simplify actions that take longer to complete — these could be affecting your prompt.

If the issue is resolved after simplifying the flow, consider splitting your logic into two separate flows or optimizing the performance of your existing flow.

I hope this information helps! If it does, please consider giving a 👍.
Best regards,
S-Venkadesh

1 people found this reply helpful.

Was this reply helpful? Yes No
vsivakumar 25 on at

Like (0)

Report
Copy link

Link copied!

The prompt takes 23seconds is that considered long for Teams, how should we handle that in Teams then

Screenshot 2025-1...
Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Was this reply helpful? Yes No
Suggested answer

Romain The Low-Code... 2,562 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

this kind of error are often related to you'r flow in error, not the agent, did you check the activity records of the flow to see how it run ? inside the activity of the flow you have lot mor detail :)

Was this reply helpful? Yes No
vsivakumar 25 on at

Like (0)

Report
Copy link

Link copied!

Was this reply helpful? Yes No
Suggested answer

S-Venkadesh 1,214 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Hi @vsivakumar,

A 17-second time span is quite high, and it can easily lead to timeouts.
We can help better if you can share a few more details:

What input are you passing to the prompt?

What instructions are you using in the prompt?

What is the expected output?

In the meantime, one recommendation is to explore whether the logic can be broken down into smaller steps so your flow can return a response faster and avoid timeout issues.

I hope this information helps! If it does, please consider giving a 👍.
Best regards,
S-Venkadesh

Was this reply helpful? Yes No