Copilot Not Working

Fix Copilot Studio SystemError from Power Automate Flow

Maira Mehtab Sep 28, 2026 869 views

Question details

The user encounters a SystemError in Copilot Studio when trying to return an HTML table generated from Outlook emails via a Power Automate flow.

How to Fix Copilot Studio SystemError from a Power Automate Flow

Product: Copilot Studio / Power Automate
Device & OS: not provided
Scenario: Integrating a Power Automate flow with Copilot Studio to retrieve Outlook emails and format them as an HTML table.
Observed behavior: The flow successfully runs in Power Automate but returns a SystemError when triggered from Copilot Studio.

Before you start

Verify that your Outlook connections in Power Automate are fully authenticated and that your Copilot Studio environment has the correct permissions to execute the flow.

Solution 1Recommended

Validate Output Formatting and Run History

Check the formatting of the data being sent back to Copilot Studio, as incompatible output types often trigger a SystemError.

Copilot Studio requires specific data formats when receiving variables from Power Automate. Complex HTML objects or tables might not parse correctly if they are not converted to string formats or Markdown before being sent back.

Review the flow output format

In Power Automate, check the 'Return value(s) to Power Virtual Agents' or Copilot node. Ensure the HTML table is passed as a string text variable rather than a raw object.

Convert HTML to Text

If Copilot Studio fails to render the HTML, add a 'Html to text' action in your flow before the final return step, or format the Outlook email data as Markdown.

Inspect the Run History

Trigger the flow from Copilot Studio, then immediately open Power Automate. Go to your flow's 'Run history' and click on the latest failed run to pinpoint which specific node or output caused the SystemError.

Validate Output Formatting and Run History

Formatting Note: Copilot Studio renders Markdown much better than raw HTML tables. Converting your Outlook email summaries into a Markdown string is often more reliable.

Solution 2

Consult the Power Platform Community

Seek assistance from Power Automate specialists for advanced connector and integration troubleshooting.

Free Microsoft Office alternative

Try WPS Office for a Seamless Productivity Experience

If complex integrations and errors in Microsoft environments are slowing down your daily workflow, consider switching to WPS Office. It provides a lightweight, highly compatible alternative to Microsoft Office, offering Word, Excel, and PowerPoint features without the heavy integration overhead or steep subscription fees.

1. Download the installer: Visit the official WPS Office website and click on the 'Download WPS Office Free' button.
2. Install WPS Office: Run the downloaded installer and follow the quick on-screen setup instructions.
3. Open existing documents: Launch WPS Office and instantly open your existing Microsoft Word, Excel, or PowerPoint files with perfect compatibility.

Highly compatible with Microsoft Office formats (.docx, .xlsx, .pptx).Lightweight installation and incredibly fast startup speed.Built-in AI capabilities to streamline writing and data analysis efficiently.Free to use with a familiar, easy-to-navigate interface for quick migration.

Frequently Asked Questions

Why does my Power Automate flow work independently but fail in Copilot Studio?

This usually occurs due to data type mismatches. A flow might run successfully and generate an HTML table in Power Automate, but if Copilot Studio cannot parse that specific raw HTML object as a standard string or text variable, it will return a SystemError.

Can I return an HTML table directly to Copilot Studio?

Returning raw HTML tables can be problematic. It is highly recommended to use an 'Html to Text' conversion action within your flow, or format your Outlook data as a Markdown string before returning it to the Copilot node.

How do I find out exactly what caused the SystemError in Copilot Studio?

The most effective way is to test the bot in Copilot Studio, trigger the error, and then immediately check the 'Run history' of your flow in Power Automate. The run details will show the exact input and output payloads, revealing where the data transfer failed.

Microsoft Copilot Issues