Child agent looping after SharePoint item update?

(1) Share

Report

Posted on by AnonymousSC

I’m running into an issue with Copilot Studio where a child agent keeps looping and never advances the topic. The child agent’s only task is to update a single column of a specific SharePoint list item using an item ID. The update itself works correctly, but after the column is written, the agent keeps calling the same “Update item” action again and again instead of stopping and returning control to the parent agent.

I’ve already tried limiting it to one execution, checking that the column is empty before updating, using flags like SummaryDone, removing user messages, and changing trigger types. Nothing stops the loop once the SharePoint update happens.

Has anyone experienced this with child agents that perform backend-only actions? Is there a recommended trigger or termination pattern to make the agent exit cleanly after a successful SharePoint update?

Categories:

Topic creation & management

Calling actions from Copilot Studio

I have the same question (1)

All responses (3)

Answers (0)

Suggested answer

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

Like (0)

Report
Copy link

Link copied!

Hello @AnonymousSC

This isn't really Copilot doing this, its the Flow.

The flow itself isn't readable but I can tell you that the conditions you are using are not stopping it and hence why it continues to trigger.

Please share clearly the following:

1) The flow Trigger Conditions

2) The flow more readable please

3) In the Flow itself, go into it and look at the Output of the Run itself for the Trigger to see what came IN and what went out. Compare that specifically to any conditions you have that will make it NOT self trigger again

One of them is wrong or not there that's why.

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
AnonymousSC 7 on at

Like (0)

Report
Copy link

Link copied!

Hi

Thanks for the response.

In this case the Flow is not self-triggering (there is no SharePoint trigger). The Flow is being explicitly invoked by Copilot Studio as a tool, and it executes and exits successfully.

The repeated runs are caused by Copilot’s planner re-invoking the same tool, not by trigger conditions inside the Flow.

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

Like (0)

Report
Copy link

Link copied!

Hi @AnonymousSC

Can you share your instructions at the Agent level?

If you click on each action that runs in the activity, what specifically made it trigger (it should show you),

But if you can explain that actual pattern and instructions at the agent level and then what your (I am assuming its an Agent Flow, or you said its a Tool, which is either a pure flow or just an action in the agent, which is it for you?

Was this reply helpful? Yes No