Notes on how to understand error messages sent from Flow Application - Answers - Salesforce Trailblazer Community
Trailblazer Community
Ask Search:
Norah AlmolaNorah Almola 

Notes on how to understand error messages sent from Flow Application

Hello, 

I get the gist of these emails when they're sent but would like a more comprehensive understanding of what each bit represents:

Subject: Error Occurred During Flow "Update_Expenses_Product_based_on_PO_Product": The flow tried to update these r...
Error element myRule_29_A1 (FlowRecordUpdate).
The flow tried to update these records: null. This error occurred: CANNOT_EXECUTE_FLOW_TRIGGER: The record couldn’t be saved because it failed to trigger a flow. A flow trigger failed to execute the flow with version ID 301w0000000H9wh. Flow error messages: An unhandled fault has occurred in this flow
An unhandled fault has occurred while processing the flow. Please contact your system administrator for more information. Contact your administrator for help.. For details, see API Exceptions (https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_calls_concepts_core_data_objects.htm).

This report lists the elements that the flow interview executed. The report is a beta feature.
We welcome your feedback on IdeaExchange (https://success.salesforce.com/ideaSearch).
Flow Details
Flow Name: Update_Expenses_Product_based_on_PO_Product
Type: Workflow
Version: 9
Status: Active
Flow Interview Details
Interview Label: Update_Expenses_Product_based_on_PO_Product-9_Purchase_Order__c
Current User: XXXXXXXX (00520000002le7o)
Start time: 14/02/2017 08:25
Duration: 0 seconds
How the Interview Started
XXXXXXXXX (00520000002le7o) started the flow interview.
Some of this flow's variables were set when the interview started.
myVariable_old = a04w000000TrCIPAA3
myVariable_current = a04w000000TrCIPAA3
RecursiveCountVariable = 3.00
ASSIGNMENT: myVariable_waitStartTimeAssignment
{!myVariable_waitStartTimeVariable} Equals {!Flow.CurrentDateTime}
Result
{!myVariable_waitStartTimeVariable} = "14/02/2017 08:25"
DECISION: myDecision
DECISION: myDecision2
DECISION: myDecision4
DECISION: myDecision6
DECISION: myDecision8
DECISION: myDecision10
DECISION: myDecision12
DECISION: myDecision14
DECISION: myDecision16
DECISION: myDecision18
DECISION: myDecision20
DECISION: myDecision22
DECISION: myDecision24
DECISION: myDecision26
DECISION: myDecision28
Executed this outcome: myRule_29
Outcome conditions: and
1. {!myVariable_current.SAGE_Product__c} (Supply & Install Cabling) Equals Supply & Install Cabling
Logic: All conditions must be true (AND)
RECORD UPDATE: myRule_29_A1
Find all Purchase_Order__c records where:
Id Equals {!myVariable_current.Id} (a04w000000TrCIPAA3)
Update the records’ field values.
SAGE_Product_Group__c = Supply & Install Cabling
Result
Failed to update records that meet the filter criteria.

Error Occurred: The flow tried to update these records: null. This error occurred: CANNOT_EXECUTE_FLOW_TRIGGER: The record couldn’t be saved because it failed to trigger a flow. A flow trigger failed to execute the flow with version ID 301w0000000H9wh. Flow error messages: An unhandled fault has occurred in this flow
An unhandled fault has occurred while processing the flow. Please contact your system administrator for more information. Contact your administrator for help.. For details, see API Exceptions (https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_calls_concepts_core_data_objects.htm)


Is there an article or release notes which help decipher the detail? 

Thank you in advance 

Norah
Best Answer chosen by Norah Almola
Jeff MayJeff May
Those emails are not really that great. They do, at least, tell you something bad happened. The best way to find out more, is to enable the Debug Log for the user who got the error (or yourself), then repeat the steps to cause the error to happen again. The Debug Log will have much more detail about what went wrong.

All Answers

Jeff MayJeff May
Those emails are not really that great. They do, at least, tell you something bad happened. The best way to find out more, is to enable the Debug Log for the user who got the error (or yourself), then repeat the steps to cause the error to happen again. The Debug Log will have much more detail about what went wrong.
This was selected as the best answer
Norah AlmolaNorah Almola
Thanks Jeff