Agent suddenly runs Flow twice

(0) Share

Report

Posted on by SamGo

Hi all,

We have an Autonomous Agent that creates E-Mail Drafts. It has been productive for almost a year.

Recently we changed the trigger flow and exported it to Productive, where it suddenly started calling its last Step (a flow that saves the draft message) twice, resulting in duplicate Drafts in the service center.

I am pretty sure this is a BUG, probably caused by changing the trigger of the Agent and causing mayhem somewhere in the agents Config but i was hoping for a more reasonable resolution.

For now we tried to "fix" it by given the Agent the Instruction not to call this flow twice. Which in general makes sense but not as a solution to a BUG - and it also did not work unfortunately.

Can anyone confirm or explain such behaviour?

Thanks Sam

Categories:

Autonomous agents

Calling actions from Copilot Studio

I have the same question (0)

All responses (3)

Answers (1)

Sort by

SM01 8 on at

Like
a
(0)

Report
Copy link

Link copied!

What trigger are you currently using ?

Also make sure there are no custom topics which is calling the agent flow at the same time.

Was this reply helpful? Yes No
Suggested answer

Sayali-MSFT Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hello,
After modifying the trigger flow and exporting/importing the solution into Production, duplicate executions can occur due to several common causes. The most likely issue is the trigger firing twice (for example due to reauthentication, connection rebinding, or multiple trigger conditions). Other frequent causes include concurrency settings resetting during deployment, agent orchestration looping back to the final step, or the save-draft flow executing duplicate create actions internally.
The recommended troubleshooting order is to check trigger run history, verify concurrency control, review agent logic paths, inspect save-flow execution history, and implement idempotency safeguards (such as unique keys or draft existence checks). Production environments often expose these issues because of stricter retry behavior, higher parallelism, and different connection handling compared to development.

Was this reply helpful? Yes No
Verified answer

SamGo 14 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi all, thanks for your suggestions. So basically what happend: Even though the old trigger flow has been deleted in all Environments, the Productive environment still triggered it. It stopped around midnight so my guess is, that the Environment didnt update until then and still had a "ghost" Flow running. I also reached out to support which contacted me after it updated so that wasnt helpful at all. Things like this do not make me happy but it is what it is. I am just wondering who is held responsible for the Copilot credits that have been used while the environment triggered a flow that wasnt even there.... But well - Just be aware of such things!

Was this reply helpful? Yes No