Power automates flow issue

(0) Share

Report

Posted on by Murphy4ever

Hi everyone,

I’m encountering a strange issue in Power Automate.

I have a flow (Flow A) that collects data from Power Pages, populates a Word document template, and then converts it to a PDF. This flow works perfectly, as shown in the attached image.

However, when I add an action, 'Send an email (V2)', to the flow (let’s call this Flow B), I receive a 400 Bad Request error when the Power Page calls this flow. Interestingly, Flow B doesn’t even run, so I can't retrieve detailed error information. When I remove the 'Send an email (V2)' action, the flow works again.

I conducted a test with a different flow (Flow C), as shown in the last image, and it worked without any issues.

I’m not sure what’s causing Flow B to fail. Has anyone experienced a similar issue or have any insights?

Thanks advance for any ideas.

Categories:

General topics

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

sannavajjala87 931 Super User 2026 Season 2 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi,

This sounds like the Power Pages trigger validation is failing before the flow even starts. Since the flow works until you add "Send an email (V2)", and the run never appears in Flow history, the issue is likely related to the flow becoming ineligible for the Power Pages trigger rather than the email action itself failing.

A few things to check:

Re-authenticate the Office 365 Outlook connection used by Send an email (V2).

Make sure all connections in the flow are healthy and owned by a valid user.

Save the flow, turn it off and back on, then republish the Power Pages site.

Try adding a very simple Send an email (V2) action with hardcoded values to rule out a dynamic content issue.

Check whether the flow is still listed as available from Power Pages after adding the email action.

I've seen cases where adding an action introduces a connection or permission requirement that causes the Power Pages trigger to return a generic 400 Bad Request before the flow is invoked. Since your standalone test flow with Power Pages → Send an email (V2) works, I'd focus on connection references and permissions in the larger flow rather than the email action itself.

Thanks & Regards,

Manoj Annavajjala

www.powerplatformengineer.com

Was this reply helpful? Yes No