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 - Copilot Studio pre-built Agent...
Suggested answer

Copilot Studio: Inconsistent execution when chaining two Dataverse tools (search + log) in an agent

(1) ShareShare
ReportReport
Posted on by 4

Hello Power Platform Community,

We’ve built a Copilot Studio agent that uses two Dataverse tools:

  1. Search Tool – queries a Dataverse table based on the user’s input.
  2. Log Tool – inserts a record into another Dataverse table to store the search details (query text, timestamp, etc.).

The agent and tools are configured so that:

  • The agent is instructed to invoke the Search Tool first, then the Log Tool.
  • The Search Tool is also instructed to invoke the Log Tool immediately after completion.
  • The Log Tool has instructions to run after the Search Tool finishes.

However, the behavior is inconsistent:

  • Sometimes both tools run correctly — the Search Tool returns results, and the Log Tool logs the query.
  • Other times, the Log Tool is not triggered at all.
  • Occasionally, the Search Tool fails to return results.
  • In some runs, the Log Tool incorrectly prompts for inputs that should be automatically passed from the Search Tool.
  • It can even alternate between working and not working (e.g., runs fine on the first query, fails on the second, then works again).

Has anyone experienced similar reliability issues when chaining multiple Dataverse tools in an agent?

Is there a known limitation or timing issue with tool-to-tool invocation in Copilot Studio?

Any suggestions, best practices, or troubleshooting steps would be greatly appreciated!

 

I have the same question (0)
  • Michael E. Gernaey Profile Picture
    51,709 Super User 2025 Season 2 on at
    Copilot Studio: Inconsistent execution when chaining two Dataverse tools (search + log) in an agent
     
    While I have not, I am super super super super... ummm the A word, when it comes to my instructions
     
    So it would be interesting to see your literal instructions, description and your tools and their descriptions (which can cause issues)
     
    If you are able to share pictures that is.
  • Suggested answer
    S-Venkadesh Profile Picture
    747 Moderator on at
    Copilot Studio: Inconsistent execution when chaining two Dataverse tools (search + log) in an agent
     
    I tested your Agent scenario using two tools:
    • Tool 1: Get Student from Dataverse table
    • Tool 2: Add Marks — in this tool, I added the related column in the Inputs section with a description (refer to the screenshot).
    I was able to get the expected output ((Refer Screenshot #3) by following these guidelines:
    • Keep instructions directive and action-oriented with Tools. (Refer Screenshot #1)
    • Add a short description for each tool to clearly explain its purpose.
    • Include a relationship field in the Inputs section with custom instructions, so the Copilot understands dependencies between tools. (Refer Screenshot #2)

       
    Screenshot #1
    Screenshot #2
    Screenshot #3

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 479 Super User 2025 Season 2

#2
Romain The Low-Code Bearded Bear Profile Picture

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

#3
DAnny3211 Profile Picture

DAnny3211 49

Last 30 days Overall leaderboard