0

I have been troubleshooting this for awhile. Not sure what I'm doing wrong. Pretty sure it's simple issue.

Below is the screen shot. I'm just trying to send an Email from a Salesforce Screen Flow when it fails. From my research, it looks like I have to do a platform event subscription in the Process Builder to get notified when a User messes up a screen. I'm not sure why this is the case.

Any suggestions?

  1. Already Checked Deliverability in the Sandbox. All emails are going out.

  2. Verified typos.

  3. verified that the template body only contains the flow error message.

Here is the article outlining the process builder / platform event.

Here is the screen shot of my core action config:

CoreActionSettings

4
  • 1
    are we talking about sending this email on a flow fault path (from say an update records element)? does the flow debug show this element even being executed? have you tried to see if a chatter post works instead?
    – cropredy
    Sep 11 '20 at 0:47
  • @cropredy that's correct, a flow that will fire off the fault paths. The value that is failing {!Opportunity.Name} that's failing in the loop. I know how to fix this error, but wanted to make sure that if other errors occurred, the email would send. I guess it's safe to say that the fault is only in if the element fails, not if the whole flow fails.
    – thinker
    Sep 11 '20 at 18:14
  • 1
    That is correct
    – cropredy
    Sep 11 '20 at 19:31
  • Very helpful. And was the correct solution. Post answer for the correct solution, and will give credit.
    – thinker
    Sep 11 '20 at 19:54
1

A flow can generate a fault on a given element (for example, an Update Records element where a Validation Rule in the database triggers):

If you connect a Flow Fault connector to, say, a Core Action like Send an Email or Post to Chatter, such core action will execute.

If the Flow fails in an uncatchable way (or omitted flow fault path), standard Flow error handling ensues.

Screen flow failures publish platform events that can be subscribed to (which can also then post to chatter, send email etc.)

SFDC Doc recommends configuring a flow fault path for every element that supports this.

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.