[SalesForce] How to Debug a flow built in process builder

I have a workflow that generates a task. Based n creating a custom object

I have been looking in the logs to make sure it's working. But, now I'm stumped. Does anyone know how to understand this?

23:18:39.26 (52354852)|WF_SPOOL_ACTION_BEGIN|Workflow
23:18:39.26 (52408728)|WF_ACTION| Flow Trigger: 1;
23:18:39.26 (52426167)|WF_RULE_EVAL_END
23:18:39.26 (53167647)|WF_FLOW_ACTION_BEGIN|09L6F000000TPxm
23:18:39.54 (54700215)|FLOW_CREATE_INTERVIEW_BEGIN|00D90000000zLUc|3006F000000HGQX|3016F0000000YRY
23:18:39.54 (56652182)|FLOW_CREATE_INTERVIEW_END|6080efeb17ccf84240e2573571cd15447f30734-4ad9|Attitude to activity
23:18:39.57 (57141012)|FLOW_START_INTERVIEWS_BEGIN|1
23:18:39.57 (57885847)|FLOW_START_INTERVIEW_BEGIN|6080efeb17ccf84240e2573571cd15447f30734-4ad9|Attitude to activity
23:18:39.57 (75536714)|FLOW_START_INTERVIEW_END|6080efeb17ccf84240e2573571cd15447f30734-4ad9|Attitude to activity
23:18:39.57 (100612709)|FLOW_START_INTERVIEWS_END|1
23:18:39.26 (100708389)|WF_FLOW_ACTION_ERROR|09L6F000000TPxm|3006F000000HGQX|Error executing flow: Attitude_to_activity, FlowDefId: 3006F000000HGQX, FlowVersionId: 3016F0000000YRY
23:18:39.26 (100734715)|WF_FLOW_ACTION_ERROR_DETAIL|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.
23:18:39.26 (101080774)|WF_FLOW_ACTION_END|09L6F000000TPxm
23:18:39.26 (101100943)|CODE_UNIT_FINISHED|Workflow:01I90000002ALag
23:18:39.26 (102260165)|EXECUTION_FINISHED

Best Answer

you might want to check out this article. https://salesforceyoda.com/2014/05/06/how-i-learned-to-stop-worrying-and-test-my-flow/

specifically you are not handling the faults for a given flow element.

"Any Record or Fast Element can have a Fault element attached to it, and your best practice is to ensure that every Record or Fast Element has a Fault element attached to it. A Fault element can be made by creating any element and drawing an arrow to it from your Record or Fast Element AFTER they already have an arrow pointing to another element. If the Flow errors on that source element, it will then perform whatever is in your Fault, rather than showing that “unhandled fault”. That’s what unhandled means; it means that you haven’t defined what should happen when a fault happen"

Related Solutions

[SalesForce] Process builder rule criteria

Try below formula if it works for you:

AND
(
   PRIORVALUE([Contact].Account.AccountNumber) = 't',
   ISNULL( [Contact].Title ),
   ISCHANGED( [Contact].AccountId )
)

You need to compare with = sign.

[SalesForce] simple process builder failing with error “failed to access the value for variable because it hasn’t been set or assigned”

Ok. I raised ticket with Salesforce on this and they came back saying it is a known issue(After more than a month of back and forth) and updated the Knowledge article with the work around for situations like these where Picklist fields are referenced in the formula.

NOTE: As mentioned in Known Issue W-2763830, this formula syntax does not work when using Formula-Based Criteria and making a cross-object reference to a Picklist field (specifically when using the TEXT or ISPICKVAL functions with the spanning reference to that picklist). If you need to make cross-object reference to a picklist field in Process Builder Criteria, use Condition-Based criteria. If you must use formula-based criteria, use the CASE function when making cross-object references to picklists.

URL to the known issue on this : https://success.salesforce.com/issues_view?id=a1p300000008aUBAAY

URL to the knowledge article: https://help.salesforce.com/articleView?id=000212174&type=1

In my case, I had to change the formula as below using CASE function instead of ISPICKVAL function:

Fails:

AND(NOT(ISBLANK([Case].AccountId)),ISPICKVAL([Case].Account.Active__c,'Yes'))

Works:

AND(NOT(ISBLANK([Case].AccountId)),CASE([Case].Account.Active__c,"Yes",1,0)=1)

Related Topic