Power Platform Community Forum Thread Details

Hi,

I am trying for several days to regsiter modification on my Bot Copilot but with an error message to blocks me to register.

What I am doing is to add a connection to powerautomate to send automatically an email.

Here is the error message I have :

"HTTP Status:BadRequest, ServiceRequestId: b791708f-0b9a-41ef-9fea-7a2015a9602b [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."}]}
Informations de diagnostic : ID de demande de service : b1c1e11e-9532-4622-914c-92402b076a6c ID de session : 120a4d40-92e0-11f0-b945-ebe153ed943f"

I have succeeded to create such connexions already , but currently it is now impossible.

Could you please facilitate ?

Best Regards.

Categories:

Using flows

The error you are experiencing when registering the Power Automate connection for your Bot Copilot—especially for sending automatic emails—is related to permission handling and connection setup within the Power Platform environment. This error often appears when plugins or connectors continue processing without correctly managing failed service calls, leading to a situation where no active transaction exists and the system aborts the modification process.

Key Issues

The error usually arises from custom plugins in the environment that do not handle service call errors correctly, failing to abort when an error occurs.

The bot may lack the required permissions to trigger the Power Automate flow, especially when service accounts are used for connections intended to perform privileged actions.

If similar connections have worked before, the issue could be due to recent changes in plugins, connections, permissions, or authentication procedures.

Steps to Fix

Check and update all custom plugins related to the modified process to ensure they abort immediately when a service call fails, and do not attempt to continue processing.

Go to the "Run only users" section in your affected Power Automate flow and make sure the service account is selected for each connector involved, such as Outlook for sending emails.

Grant explicit permission for your Copilot bot or related service account to run the flow, ensuring the bot identity has the necessary access to all resources involved.

If you recently changed any connections in your flow, refresh the metadata and republish your bot to ensure it references the updated connection settings.

For authentication issues, add an authentication action in Copilot Studio before triggering the flow to ensure user identity and delegated permissions are properly managed.

If previous bot versions or connection errors persist for some users, increment the bot app manifest version, upload it to Teams Admin Center, and have users clear their Teams cache to force the update.

If manual troubleshooting does not resolve the issue, seek administrative support within your organization or from Microsoft, providing the complete error details and service request IDs.

Following these steps enables a smoother interaction between Copilot Studio bots and Power Automate flows by ensuring connections, permissions, and plugin logic are properly aligned.