Power Platform Community Forum Thread Details

Hi,

The error InvokerConnectionOverrideFailed — Could not find any valid connection for connection reference name 'shared_sendmail' in APIM header means the flow has a reference to the Mail connector (the "Send an email notification" / Notifications connector) but Power Automate can't find a backing connection in your current environment to satisfy it. shared_sendmail is the internal ID of the Mail / Notifications connector — the one that sends from microsoft@powerapps.com.

Why this surfaces when you touch the Process Documents output

It's almost always one of three patterns:

The flow was copied / imported / built from a template and brought a Send an email notification (V3) action with a connection reference baked in. The reference object exists in the flow JSON, but no actual connection has been created in this environment yet.
The flow lives in a solution and the connection reference component is present but not bound to a valid connection in the current environment. Solutions require connection references to be re-bound per environment. Reference: Connection references in cloud flows.
The Send an email action was added then deleted, but the connection reference object was left behind in the flow definition.

Fix — in order of fastest to most thorough

Create the connection explicitly. Go to Power Automate → Data → Connections → + New connection, search for Mail (publisher: Microsoft, icon is a small envelope — not Outlook 365), and click Create. There's no sign-in prompt because it's a service-managed connector. Reference: Manage connections in Power Automate.
Open the flow → Edit → click the Send an email notification (V3) action → the "…" menu → "My connections" → pick the connection you just created. Save. If the action shows a yellow warning triangle, that confirms the binding was missing.
If the action isn't actually in the flow anymore (you got the error while only touching Process Documents output), the leftover reference is still in the flow JSON. Add a throwaway Send an email notification (V3) action, bind it to the new connection, then delete it again. That forces the flow to re-emit a valid reference list on save.
If the flow is inside a solution, open Solutions → [your solution] → Connection references and make sure a Mail connection reference exists and its Connection field is populated for this environment. Re-export/re-import isn't needed for this — just set the connection on the reference record. Use connection references and environment variables.

About using Process Documents outputs in the Send an email action

Once the connection binding is fixed, you can pass any of the Process Documents outputs (extracted fields, confidence scores, original file content) directly into the Body, Subject, or To fields via dynamic content. Daily send caps on the Mail connector are documented at the connector reference — currently 100 emails/24 hours per user and up to 1 MB body / 10 MB attachment. Reference: Mail connector limits and Process documents with AI Builder in Power Automate.

If the error persists after binding the connection

Check whether you have two "Send an email" actions in your action picker — Power Automate ships both Send an email (V2) (Outlook 365 connector, ID shared_office365) and Send an email notification (V3) (Mail connector, ID shared_sendmail). The error message names shared_sendmail, so the action that needs the connection is specifically the Notifications one, not Outlook. If you'd rather send through Outlook (works around Mail connector daily caps and gives a real sender), swap to Send an email (V2) and authenticate with your work account. Reference: Office 365 Outlook connector.

Net: create a Mail connection in Data → Connections, re-bind the action to it, and the InvokerConnectionOverrideFailed goes away. If you're in a solution, also set the connection on the corresponding connection reference record.

Found this helpful? Please mark ✅ "Does this answer your question?" so others searching for the same issue can find it quickly. A 👍 on "Was this reply helpful?" or a ♥ Like is also much appreciated!

Raghav Mishra — LinkedIn | PowerAI Labs