cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
PaulB1
Frequent Visitor

Bug on Send Email in Flow.

In this flow I created 2 days ago I take some HTML and convert it to PDF and then the last step added was to email the output. 2 days ago it worked well. Yesterday and today it fails.

I have tried Office 365 send email and Outlook send email and nothing seems to work.

 

I have attached 2 screen shots of the flow. One showing how the flow looks and the second of the details of the send mail. It is not a complicated send mail. I have one or two receipents, a subject, body (tried both with and without the HTML passed from Powerapps) and an attachment which is the PDF created from earlier steps in the flow process. The isHTML - tried with both Yes and No.

 

I have deleted the step and reinstated it many times to no avail.

 

Without the send email step the flow works perfectly. 

 

All assistance is gratefully received.

Thank you

Flow errorFlow errorEmail stepsEmail steps

2 ACCEPTED SOLUTIONS

Accepted Solutions
PaulB1
Frequent Visitor

For some reason the Flow had become disconnected from the PowerApps Application. So registering the Flow in the appropriate place in the App made it work again. Strange.

The clue is in the error message where it mentions the X-MS-APIM-Tokens. Not an easy one to follow and a lot of trial and error to fix this undocumented feature.

Perhaps MS might update their documentation.

 

 

View solution in original post

That is an error I've experienced few months ago. I posted it from my employer (at that time) account: 

https://powerusers.microsoft.com/t5/I-Found-A-Bug/Unable-to-process-template-language-expressions-in...

 

It just happens from time to time. Reasons? No one knows. Solution:

  • Test Flow with manual trigger (to reattached all connectors).
  • export -> import flow
  • make new flow (or new register). 

 

View solution in original post

2 REPLIES 2
PaulB1
Frequent Visitor

For some reason the Flow had become disconnected from the PowerApps Application. So registering the Flow in the appropriate place in the App made it work again. Strange.

The clue is in the error message where it mentions the X-MS-APIM-Tokens. Not an easy one to follow and a lot of trial and error to fix this undocumented feature.

Perhaps MS might update their documentation.

 

 

That is an error I've experienced few months ago. I posted it from my employer (at that time) account: 

https://powerusers.microsoft.com/t5/I-Found-A-Bug/Unable-to-process-template-language-expressions-in...

 

It just happens from time to time. Reasons? No one knows. Solution:

  • Test Flow with manual trigger (to reattached all connectors).
  • export -> import flow
  • make new flow (or new register). 

 

Helpful resources

Announcements
MPA Virtual Workshop Carousel 768x460.png

Register for a Free Workshop

Learn to digitize and optimize business processes and connect all your applications to share data in real time.

Microsoft Build 768x460.png

Microsoft Build is May 24-26. Have you registered yet?

Come together to explore latest innovations in code and application development—and gain insights from experts from around the world.

May UG Leader Call Carousel 768x460.png

What difference can a User Group make for you?

At the monthly call, connect with other leaders and find out how community makes your experience even better.

PA Survey Carousel Image.png

We want to hear from you!

If you are a small business ISV/Reseller, share your thoughts with our research team.

Top Solution Authors
Users online (1,360)