Respond to Flow Error Emails
- Nickolette De Clerck
- Abraham Lloyd
This page captures how to view runtime exceptions generated by Salesforce Flow caught by Cuneiform® for CRM and Cuneiform® for Data Cloud during its use. Use this guide to learn how to inspect the details generated by these exceptions.
APPLIES TO | CUNEIFORM FOR CRM CUNEIFORM FOR DATA CLOUD
Table of Contents
What May Trigger a Flow Application Error Email?
Cuneiform for CRM data profiling leverages Salesforce flow, which may generate exceptions and alert emails if an exception is handled within one of our packaged flows.
Alert emails include necessary IDs to guide your Cuneiform for CRM Admins in troubleshooting what happened and why, whether this is due to an attempt to profile an unsupported field or other reasons.
Please see Known Product Issues on what to avoid and View Caught Profiling Exceptions for more information on how and why we create exception logs and how to troubleshoot your processes effectively.
Handling Flow Application Error Emails
Cuneiform for CRM Admins can follow the steps below to identify where a problem occurred, troubleshoot the issue further, or contact support.
Get the Process ID from the Error Email
The Process ID follows the Automated Process in the Flow Application Error email, as highlighted below.
Search your Org to Find the Process Details
Paste the Process ID from the Flow Application Error Email into your Salesforce org’s search bar.
Find the Exception and the Exception Log Entry
You can search for the keyword “Exception” to identify problem spots, find the flow, and find out where the exception occurred.
You can click on the Exception Log ID to see a summary and navigate to exception details.
Follow the Steps in View Caught Exceptions
This page explains how to review data profiling exceptions caught via our logging. You can use this article to familiarize yourself with our exception log format and the types of captured exceptions.
Contact Support if You Cannot Find the Exception Log ID
There may be cases where the exception is obfuscated, and no additional details are logged in the Profiling Exception Log. In such cases, don't hesitate to contact our support team and forward the flow exception email to assist in further troubleshooting.