Copilot Studio

Copilot Studio agent error with trigger concurrency and SystemError

(0) Share

Report

Posted on by ML-18030837-0

Hello community,

I am encountering repeated errors when working with my Copilot Studio agent flow. The issues include:

InvalidConcurrencyConfiguration when using a manual request trigger with a response action.
CannotDisableTriggerConcurrency when trying to remove concurrency from the manual trigger.
A SystemError with Conversation ID: ae017535-76d7-43a7-aa6d-a151418c5ecc at UTC time 3/18/2026 8:22:39 AM.

It seems concurrency configuration cannot be removed once applied, and response actions require operationOptions = asynchronous if concurrency is enabled. However, I am still blocked from saving or running the flow.

Could someone from Microsoft or the community advise on:

The correct way to resolve this concurrency conflict with response actions.
Whether recreating the manual trigger is the only option.
How to handle the SystemError — is this a transient runtime issue or something requiring support escalation?

Thank you for your guidance.

Categories:

Calling actions from Copilot Studio

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Vahid Ghafarpour 817 on at

Like
a
(0)

Report
Copy link

Link copied!

In Copilot Studio / Power Automate flows, a manual trigger with a “response” action (returning data to Copilot) behaves like a synchronous request/response flow but when you enable concurrency control, the system treats it as asynchronous execution possible.

That’s why you see InvalidConcurrencyConfiguration

Was this reply helpful? Yes No
Suggested answer

ML-18030837-0 2 on at

Like
a
(0)

Report
Copy link

Link copied!

So how do i fix the flow?

Was this reply helpful? Yes No
Suggested answer

deepakmehta13a 369 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi,

You’re hitting a known limitation with manual (agent) trigger + response action + concurrency.

To fix it:

Use synchronous pattern (recommended)

Open trigger settings

Turn OFF concurrency control (if possible)

Keep the Respond to Copilot action

If it doesn’t allow disabling → recreate the trigger (this is often required once concurrency is enabled).

Or switch to async pattern

Keep concurrency ON

Remove the response action

Handle output separately (e.g., store result or send message later)

About SystemError
This is usually a side effect of invalid configuration, not a separate issue. It should resolve once the trigger setup is corrected.

In short:
Response action + concurrency = conflict
So either remove concurrency or remove response action.

Hope this helps.

If this helps resolve your issue, please consider marking the response as Verified so it can help others facing a similar scenario.

If you found this helpful, you can also click “Yes” on “Was this reply helpful?” or give it a Like.

Was this reply helpful? Yes No