Error in flow sending email

[terrieb]

We created a flow for an ipad request that is set to send an email based on two conditions:

1.  If the request is denied, then the email is sent to the requested for's email

2.  If the request is approved, the an email is sent to the requested for's email.

The first request created using this new flow worked just fine.

However, since then, starting on the very next request created the next day, the emails are no longer being sent and the flow errors out.

In checking the executions, both have the same message:  Access denied to create new email

I checked the email logs and they are not showing there as either skipped or failed.

Nothing else has changed on the instance, so is there a reason why these are no longer working?

See attachment for screen shots.

[Nilesh Wahule · Accepted solution]

Hi @terrieb ,

Please check the flow properties if the flow is set to run as system user. Also have a look at this post 

Getting "Access denied to create new email" in Flow Designer since upgrading to Vancouver

---------------------------------------------------------------------------------------------------

Please mark my answer as helpful/correct if it resolves your query.

Thanks,
Nilesh Wahule

---------------------------------------------------------------------------------------------------

[Nilesh Wahule · Accepted solution]

Hi @terrieb ,

Please check the flow properties if the flow is set to run as system user. Also have a look at this post 

Getting "Access denied to create new email" in Flow Designer since upgrading to Vancouver

---------------------------------------------------------------------------------------------------

Please mark my answer as helpful/correct if it resolves your query.

Thanks,
Nilesh Wahule

---------------------------------------------------------------------------------------------------

[terrieb · Accepted solution]

Set the advanced properties to System User in our non-prod instance and tested impersonating someone without the admin role.  That appears to have fixed it.

Set it in Production instance as well and asked a person without the admin role to test it for me.  Hopefully this fixes it.  

If it does, I will mark this as "Accept as Solution".  

Thank you

[Nilesh Wahule]

Hi @terrieb ,

Hope you are doing well !!

Did my reply answer your question?

If my response helped, please mark it correct/helpful  and close the thread so that it benefits future readers.

---------------------------------------------------------------------------------------------------

Thanks,
Nilesh Wahule

---------------------------------------------------------------------------------------------------