Power Platform Community Forum Thread Details

Hi everyone,

I am building an automation where a user uploads a PDF to a Copilot Studio Agent. This triggers a Power Automate flow that:

1. Extracts the report date using AI Builder.
2. Checks a SharePoint list to see if a report for that date has already been processed.

The Requirement:
If the report date already exists in SharePoint, I need the flow to stop immediately and the Agent to tell the user: "This report has already been processed."

The Challenge:
I am struggling with the best way to "Send a message" back to the chat from inside a specific branch of the flow.
1. Multiple Respond Actions: I tried adding a 'Respond to the agent' action inside the 'True' (Duplicate Found) branch, but I keep getting Schema Errors because I also have a 'Respond' action at the end of the success path.
2. Terminate Action: If I use a 'Terminate' action to stop the flow, the Agent often shows a generic system error instead of my custom "Duplicate Found" message.

Overall, In chat user should get the message like the report has been proceed already, but they're not getting any message or i am not able to find any actions that can send a message to agent(in chat bot) ...

My Questions:

What is the standard practice for sending a "Short-circuit" or "Validation Error" message from a Flow to a Copilot Agent?
Do I need to use a specific Variable strategy to pass a Status Message back to the Agent?
How can I ensure the Agent speaks the error message before the flow completes or terminates?
Any guidance on how to properly map these validation messages back to the chatbot interface would be a huge help!

Categories:

Autonomous agents

Calling actions from Copilot Studio

Hi,

1. Standard practice

You should have only ONE “Respond to the agent” action in the flow.

Instead of placing multiple Respond actions in different branches, the recommended approach is:

Use a Condition (duplicate check)
Set variables like:
- Status (e.g., Success / Duplicate)
- Message (e.g., “This report has already been processed.”)
Let the flow continue
Use a single Respond to the agent at the end

This avoids schema conflicts and keeps the contract consistent.

2. Variable strategy

Yes, using variables is the cleanest approach.

Example:

Initialize:
- statusMessage (string)
- isDuplicate (boolean)

Then:

If duplicate:
- Set statusMessage = "This report has already been processed."
- Skip further processing (don’t terminate)
Else:
- Continue processing
- Set success message