Email Log does not capture record of email generated using "Send Email" Flow Action

Xavier_Wharton
Giga Guru

Hello Everyone, 

I noticed that when I test a flow in either of my sub-prod instances (DEV or TEST), the email that should be generated from the Send Email action does not show up in the email log, nor does it route to the test email address that I have set up in the Email Properties module. 

However, when I push the flow to production, it works without issue. 

Moreover, in sub-prod instances, I've noticed that if the "Send Email Action" is set to happen before an action such as "Create Catalog Task," the Send Email action's inability to generate, prevents the generation standard emails associated with the Create Catalog Task.
 
All other emails work fine in the sub prod instances. 

Has anyone else experienced this, and if so, is there a workaround that will allow me to test the feature properly? 

Xavier_Wharton_0-1746109166019.png

 



1 ACCEPTED SOLUTION

Xavier_Wharton
Giga Guru

Thank you @BrianProvencher and @Maks 

I discovered what the issue was. 
In the recipient fields, I separated the emails with a semicolon instead of a comma, however, Flow Designer did not throw an error. The comma versus semicolon distinction stood out when I checked existing flows that utilized the same action. 

Sometimes the most minor things can hold up the flow. 😅


View solution in original post

4 REPLIES 4

Ankur Bawiskar
Tera Patron
Tera Patron

@Xavier_Wharton 

ideally should not happen and should not have any dependency on before or after catalog task action

the behavior should be same in lower instances as well

I believe you should debug in lower instance and come up with some pattern

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

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

BrianProvencher
Giga Guru

Might check your email properties in subprod. I know our email properties in subprod are different than our prod ones.

Maks
Tera Guru

We use the "Send Notification" action instead.

 

Maks_0-1746111275248.png

 

Xavier_Wharton
Giga Guru

Thank you @BrianProvencher and @Maks 

I discovered what the issue was. 
In the recipient fields, I separated the emails with a semicolon instead of a comma, however, Flow Designer did not throw an error. The comma versus semicolon distinction stood out when I checked existing flows that utilized the same action. 

Sometimes the most minor things can hold up the flow. 😅