Can't add any flow into topics - Internal Server Error - There is no active transaction

(2) Share

Report

Posted on by UL-03101329-0

Hello community,

I'm facing a strange issue and I couldn't find any idea to fix it.

Few days ago while I was modifying a topic on my copilot studio agent, I received the following error message when trying to save it :

[0x80040265:IsvAborted]
{"statuscode":500,"statusdescription":"Internal Server
Error","errors":[{"code":10000,"message":"There is no active
transaction. This error is usually caused by custom plug-ins that ignore
errors from service calls and continue processing."}]}

Since this moment I can't add or modify any flow into any topic in any agent on my environment.

I even tried creating a new topic on a new agent with a new flow and when I link this flow into my topic I can't save the changes and I get this error.

Could you help me find some explanation ?

Regards

Ugo

I have the same question (1)

All responses (1)

Answers (0)

Suggested answer

Prasad-MSFT Microsoft Employee on at

Like (0)

Report
Can't add any flow into topics - Internal Server Error - There is no active transaction

This error ([0x80040265:IsvAborted] with "There is no active transaction") is a Dataverse platform error. It usually means there’s a problem with the underlying environment or a custom plugin/extension in your Dataverse (Power Platform) instance that is interfering with Copilot Studio’s ability to save changes.

Possible causes:

A custom Dataverse plugin or workflow is failing or aborting transactions.

The environment is in an inconsistent state due to a previous failed operation.

There may be a recent update or deployment that introduced a bug or broke a dependency.

Troubleshooting steps:

Check for custom plugins:

If your environment has custom Dataverse plugins, workflows, or Power Automate flows, review their recent changes or disable them temporarily.

Try in a different environment:

Create a new Copilot Studio agent in a fresh Dataverse environment (not just a new agent in the same environment). If it works there, the issue is environment specific.

Clear browser cache and try a different browser:

Sometimes UI caching can cause issues, but this error is likely server-side.

Check Dataverse health:

Go to Power Platform Admin Center → Environments → [Your Environment] → Resources → Plugins and review any failed plugin executions.

1 people found this reply helpful.

Was this reply helpful? Yes No