Copilot Studio

Execute Copilot and wait

(0) Share

Report

Posted on by WR-18111929-0

27 Season of Giving Solutions 2025

Hello,

I have an issue with 'Execute Copilot and wait' by Microsoft Copilot Studio connector.

When I am using this action within Power Automate I receive lastResponse value in output body of the 'Execute Copilot and wait step'.

When using same action within Copilot Studio (in topic, as tool node, or as a tool separately) I got only conversation ID.

Can anyone help with that?

Categories:

Calling actions from Copilot Studio

I have the same question (0)

All responses (8)

Answers (0)

Sort by

Suggested answer

Michael E. Gernaey 53,963 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi @WR-18111929-0

Can you make sure you are not accidentally using Execute Copilot action instead of Execute Copilot and Wait action, because the first only gives the ID, the second waits.

If these suggestions help resolve your issue, Please consider Marking the answer as such and also maybe a like.

Thank you!
Sincerely, Michael Gernaey

Was this reply helpful? Yes No
WR-18111929-0 27 Season of Giving Solutions 2025 on at

Like (0)

Report
Copy link

Link copied!

No, I am not. I have a 'Response' value, but the only content is conversation id. With Power Automate works fine.

Was this reply helpful? Yes No
Michael E. Gernaey 53,963 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi @WR-18111929-0

Can you please share the flow XAML (code view) from CP.

I am going to try to reproduce it myself. It is very possible that since you are in CP it just doesn't do it because you can grab it differently... but let me check

Was this reply helpful? Yes No
WR-18111929-0 27 Season of Giving Solutions 2025 on at

Like (0)

Report
Copy link

Link copied!

Sure,

I am trying to call it as a tool, but it is the same story when calling tool within a topic.

Code view of the tool configuration:

kind: TaskDialog

response:

activity:

mode: Generated

inputs:

- kind: ManualTaskInput

propertyName: Copilot

value: cr532_knowledgeQAAssistant

- kind: ManualTaskInput

propertyName: message

value: What is clockwork owl?

modelDisplayName: Tool Assistant

modelDescription: An agent that answers user questions accurately about different Fairy-tales Creatures and Animals.

outputs:

- propertyName: Response

action:

kind: InvokeConnectorTaskAction

connectionReference: default_AIME.shared_microsoftcopilotstudio.shared-microsoftcopi-11f2e197-499f-48dd-a4bf-5de6c4b9a1b1

connectionProperties:

mode: Invoker

operationId: ExecuteCopilotAsyncV2

outputMode: All

Was this reply helpful? Yes No
SA-23011339-0 2 on at

Like (0)

Report
Copy link

Link copied!

Merhaba, kullandığım Power Automate masaüstü uygulamasında "sürüş ve bekleme" eylemi yok. Etkinleştirilebilecek bir ayar var mı?

@Michael E. Gernaey

Was this reply helpful? Yes No
WR-18111929-0 27 Season of Giving Solutions 2025 on at

Like (0)

Report
Copy link

Link copied!

@Michael E. Gernaey yep, I am sure.

Was this reply helpful? Yes No
RP-29011448-0 2 on at

Like (0)

Report
Copy link

Link copied!

gHi,

I found a bug, both Execute Copilot and Wait, and Execute Copilot have the same output bindings when called from a Copilot Studio Topic.
Acordin to the documentation:https://learn.microsoft.com/en-gb/connectors/microsoftcopilotstudio/#execute-agent-and-wait

Execute Copilot and Wait should expose:
Name   Path   Type   Description
lastResponse   lastResponse   string
The last text response in the activities list

responses   responses   array of string
The list of string responses in the activities list

conversationId   conversationId   string
The conversation ID associated with the response

Can you fix it please?
I would really like to use the response of Execute and Wait

Was this reply helpful? Yes No
CU13020412-0 2 on at

Like (0)

Report
Copy link

Link copied!

Hey @Michael E. Gernaey, facing the same issue. Not sure who the right person to tag here is, please let us know who we can reach out to for a fix.
I've tried using agent flow to invoke the agent, and using the agent flow within the copilot agent, but that has a timeout of 2 mins that doesn't seem to be configurable :/

Was this reply helpful? Yes No