4

Asking here to see if anyone knows about this interaction, and hoping to avoid initiating another month or more of frustration trying to work through Salesforce's Customer Support.

The situation is as follows:

  1. A user is creating a new Case through the Lightning UI
  2. User is providing a Contact for the case, and is checking the "Send notification email to contact" box
  3. "Save" button is clicked, starting the record insertion
  4. A Process is being run, which has an immediate action that updates the Case record being inserted
  5. The notification email does not get sent to the contact

This is only an issue when the case is created from the Lightning UI. When testing the same scenario, but from the Classic UI, the notification email is sent.

My org is very heavily customized, and the Case object has Process(es) (built using Process Builder), Workflow rules, and a trigger. I don't think those details are relevant though, because I was able to reproduce this in my personal developer edition org (which is still pretty vanilla) by simply creating a process that updates the newly inserted Case record.

What is it about Lightning that causes this failure? Is there a workaround (other than not using Lightning)?

+edit: The following critical update(s) have been applied to the org we're testing this in, prior to our tests for this issue:

  • Stop Automated Field Updates from Suppressing Email Notifications
  • 1
    Have you looked at testing in an org with the Stop Automated Field Updates from Suppressing Email Notifications critical update activated? – Kris Goncalves Feb 10 at 16:43
  • You can write a process (using PB) to notify the Contact? Why rely on that box? – Maneesh Feb 10 at 16:57
  • 1
    I got the same result. I was able to replicate your issue in a trailhead org (just one PB that updates a field on case). I also tried with the Evaluate Criteria Based on Original Record Values in Process Builder critical update activated and the problem still exists. The checkbox to send the email works fine as soon as the PB is deactivated – Kris Goncalves Feb 10 at 17:16
  • 1
    @KrisGoncalves Always good to know I'm not the crazy one (or just missing something simple like that critical update). – Derek F Feb 10 at 17:22
  • 3
    Sounds a bit like this known issue: success.salesforce.com/issues_view?id=a1p3A000001YnJRQA0 – Kasper Feb 10 at 19:46
2
+150

At Derek's suggestion I'll turn my comment into an answer:

The problem sound like the known issue Send Notification Email to Contact on Cases does not send email. If I remember correctly this issue had been in review for quite some time, so requesting an update from support may unfortunately be in order.

There's also this known issue, which sounds similar, and may have the same underlying cause: "Send Email Notification to Contact" failing to trigger email in lightning when flow is attempting to create associated asset.

The last updated date on that case is 2019-06-27 (currently 7 1/2 months) and it's still in review. Depending on your patience, you may want to request an update on that case as well.

| improve this answer | |
1

As a workaround, if you can put the record update into a scheduled action rather than an immediate action, then the email notification will be sent.

The minimum time delay for a scheduled action appears to be 1 hour.

Being able to create a scheduled action in Process Builder means that you need to:

  • Have your process set to execute only on record creation, and/or...
  • Have your criteria node set to only trigger "when specified changes are made to the record" (under the "advanced" accordion menu)

This does impose some restrictions that may make the workaround non-viable for some.

For my org though, having the email sent out is vital. An hour delay is less than ideal, but it beats needing someone to use data loader or anonymous apex every day.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.