Skip to main content
Topics#FlowsPregunta de Nich Weidman
Nich Weidman preguntó en #Flows
Ayer, 17:38

Tracking Down Mystery Automated Email

We have a process we're updating that involves sending out an automated email when a new record is created on a custom object.  Everything tested out in Sandbox, but when migrated to Prod, two slightly different emails are triggering when I test.  Talking with the internal customer, they said, "Yeah, that's always been going out," but they don't know who originally set it up.   

 

  • It would have been set some time before me...but it's not triggering in Preprod, which has been refreshed recently - so I'd think it would.
  • Checking Flow triggers, the only other flow triggering off of that custom object updates a field - there are no send email elements to it.
  • I don't see any legacy email alerts or Workflow actions for it
  • I turned off my Flow, opened a debug log on the automated process user, and nothing generated when I triggered that mystery email (that still came through.)

 

I'm kind of at a loss to figure out where to check from here. 

 

#Flows  #Email  #Flow  #Automation

3 respuestas
  1. Smitha Thomas (CIBC) Forum Ambassador
    5 oct, 23:27

    Hi @Nich Weidman

     

    When Salesforce sends a system email, it includes special header fields that identify the source organization and user. To identify the source, locate the following fields in the raw email headers:

    • X-SFDC-LK — The Salesforce Organization ID (the 15- or 18-character org ID of the org that sent the email).
    • X-SFDC-User — The Salesforce User ID of the user whose automation triggered the email.
    • X-SFDC-EntityId — The record ID of the Salesforce entity (such as a workflow rule or report) that triggered the email.
    • X-SFDC-Emailcategory — The category of the email (for example, workflow, report, or Chatter digest).
    • X-SFDC-ORGTYPE — The type of org that sent the email. Note: this field only appears in emails sent from Free or Trial orgs. It does not appear for production, sandbox, or developer org emails.

    Important:

    Use the original .msg formatted email — not a forwarded copy. Forwarding an email overwrites the original headers, making it impossible to identify the source org. 

     

    Find the User Id from

    X-SFDC-User

    then go to set up and add a Debug trace for the user and then triggert the email. This will create a debug log for you to read and find the source. 

     

    Check out these articles for more info:

    1. Find the email headers for emails
    2. How to Identify the Salesforce Organization That Sent a System Notification Email 

       

Escribir una respuesta...
0/9000