Unanswered

Power Automate "Sends a Prompt to the Specified Copilot for Processing" Not Triggering

(2) Share

Report

Posted on by SG-01040448-0

Hello Microsoft Copilot Studio Community,

I am encountering an issue while creating a Power Automate flow that involves the "Sends a prompt to the specified copilot for processing" node. Despite setting up the flow correctly, the node does not seem to trigger the Copilot agent as expected. Here's a detailed breakdown of the situation:

Flow Overview

The flow is designed to trigger when a task is assigned. It performs the following actions:

Retrieves the task title.
Sends a response containing the task title.
Sends a prompt about the new task to a specified Copilot for processing.

The Problem

While the flow executes the first two steps without any issues, the third step—sending a prompt to the Copilot—does not work. The Copilot agent does not respond or show any indication of receiving the prompt. There are no error messages in the flow, and the output seems to be configured correctly.

Troubleshooting Steps Taken

Verified the flow's configuration to ensure all parameters are set correctly.
Checked the connection between Power Automate and the Copilot Studio.
Tested the flow manually to confirm that the issue is isolated to the "Sends a prompt" node.

Request for Assistance

Has anyone else faced a similar issue? If so, how did you resolve it? Are there specific settings or configurations I might be overlooking? Any insights or suggestions would be greatly appreciated.

Thank you in advance for your help!

Categories:

Building flows

Screenshot 2025-0...

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

Michael E. Gernaey 53,323 Super User 2025 Season 2 on at

Like (1)

Report

Hi @SG-01040448-0

Please open a flow run that appears to a have run without error. Note: just because it finishes doesn't mean it worked.

Look at the actions themselves, very closely to see exactly what was input and output.

Validate what you put into the configuration of the actions.

Also note that using Set variable in a loop, unless you turn on concurrency and set it to 1, can and will cause you issues, because it is not thread safe.

So it can and will over time cause things to fail due to bad data consistency. But I have to ask. Why do you have a Set variable inside a loop? Can you share the expression you are using.

Also, as a test, after sharing pictures of your config etc and of the run and the inputs and outputs of that, can you please set the For Each to concurrency on and value 1 and test again please.

Thanks

Was this reply helpful? Yes No
SG-01040448-0 4 on at

Like (0)

Report
Hi @Michael E. Gernaey,

Thank you for your response and for providing detailed suggestions!

To address your points:

I'm attempting to extract task details, like the Task Title, from the Planner Task trigger and then pass them to the Copilot agent for processing.

Following your advice, I set the concurrency on the "For Each" loop to 1. Unfortunately, this adjustment did not resolve the issue.

I have attached screenshots of my configuration for your reference, including the inputs and outputs from the flow run.

Additionally, I wanted to highlight an observation: the flow works perfectly in Copilot Studio's test console, and I receive the expected output there. However, the issue arises when the flow is deployed—the prompt to the Copilot agent fails to execute as intended.

Could you please advise on what might be causing this discrepancy between the test environment and the deployed agent? Your insights would be greatly appreciated.

Thanks once again for your support!

Best regards,
Shubham

Screenshot 2025-0...

Screenshot 2025-0...

Was this reply helpful? Yes No
Michael E. Gernaey 53,323 Super User 2025 Season 2 on at

Like (0)

Report

Hi @SG-01040448-0

I am reviewing now

Was this reply helpful? Yes No
Suggested answer

Michael E. Gernaey 53,323 Super User 2025 Season 2 on at

Like (0)

Report

Hi @SG-01040448-0

I am sorry for the long delay.

So.. what is weird is after looking at the Connector. All this does is gets you the conversation id assigned to your request. It doesn't actually send back the response.

Looking at this.. I do not even SEE an action that you can use that ID to get the message back in Power Automate.

Microsoft Copilot Studio (Preview) - Connectors | Microsoft Learn

So I believe you now have to use an HTTP Get to get the actual response using the Conversation Id.

I am positive.. this is how you have to do it for now at least as I do not see any other way to do it.

Was this reply helpful? Yes No
SG-01040448-0 4 on at

Like (0)

Report

Hi Michael E. Gernaey,

Thank you for pointing me in the right direction regarding using the conversation ID and making an HTTP GET request. I appreciate your guidance so far!

To get started, could you kindly elaborate on how I should structure the HTTP request to fetch the response body using the conversation ID? For instance, what endpoint should I use, and are there specific headers or parameters I need to include? Any examples or further details would be immensely helpful.

Looking forward to your advice!

Was this reply helpful? Yes No