Considerations for Flow Error Emails

General

• If the user who started the flow doesn’t have a first name, null replaces the user's first name in the How the Interview Started section.
• Variable assignments display in this pattern: {!variable} (prior value) = field/variable (new value). If the variable had no prior value, the parentheses display as empty. For example: {!varStatus} () = Status (Delivered)
• If you install a non-template flow from a managed package, error emails for that flow’s interviews don’t include any details about the individual flow elements. The email is sent to either the user who installed the flow or the Apex exception email recipients.
• Failed flow interviews for these flow types that are built with the free-form layout in Flow Builder are saved and available to open in Flow Builder.
  • Screen flows
  • Record-triggered flows
  • Schedule-triggered flows
  • Autolaunched flows that aren’t triggered
• Failed flow interviews aren’t saved if:
  • The flow is installed as part of a managed package and isn’t a template.
  • The failure occurs after the flow interview is paused and then resumed at least one time.
  • The error is handled because the element that encounters the error is connected to a fault connector.
  • The failure occurs during an Apex test method.
  • The flow is a standard flow.
  • The value of the flow’s metadata field status is Draft or InvalidDraft.
  • The failed flow interview exceeds 1 MB.
  • The failed flow interviews already saved in the database exceeds 1 GB.
• Failed flow interviews don’t count toward data, file, or paused flow interview storage limits. When failed flow interviews are saved, they’re available for up to 14 days and then automatically deleted from the database.
• These limits apply when failed flow interviews are saved.
  • For any specific flow, no more than 100 failed flow interviews are saved in a 24-hour period.
  • For a batch of up to 200 failed flow interviews in the same transaction, one interview is saved.
  • Across all the flows in an organization, no more than 3,000 failed flow interviews are saved in a 24-hour period.
  • Failed flow interviews exceeding 1 MB aren’t saved.
  • Failed flow interviews aren’t saved if more than 1 GB of failed flow interviews are already saved in the database.

Screen elements

Password fields display in plain text

Subflow elements

• The merge field annotation ({!variable} as opposed to just variable) is missing for variables in a referenced flow. For example, when an interview enters a subflow and gives details about the inputs, the subflow's variable is subVariable instead of {!subVariable}.
• If the error occurs in a referenced flow, the email is sent to the author of the parent flow, but the subject references the name of the referenced flow.
• If you see multiple Entered flow ReferencedFlowName version ReferencedFlowVersion messages with no Exited ReferencedFlowName version ReferencedFlowVersion messages in between them, the flow user navigated backwards. To prevent this scenario, adjust the navigation options in the first screen of the referenced flow so that the user can’t click Previous.