If you’ve used Salesforce’s Visual Workflow aka Flows or process builders, chances are you’ve come across an error like this:
First exception on row 0; first error: 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 301i0000000LyvR. Flow error messages: <b>An unhandled fault has occurred in this flow</b><br>An unhandled fault has occurred while processing the flow. Please contact your system administrator for more information.
That really doesn’t tell ya much other than an error happened. Up until today, I’d troubleshoot it by running the operation manually so that I’d receive the “error email” that contains all the details as to why it failed and which process builder or flow is having the issue. However, if you aren’t receiving the error email, it can be rather challenging to identify the flow or process builder having the issue, especially if someone changed one of these in production and now the unit tests are failing and stopping your deployment.
Trying to open https://…salesforce.com/301i0000000LyvR results in an “insufficient privileges” error page.
Open https://…salesforce.com/designer/designer.apexp#Id=YOURFLOWIDHERE where YOURFLOWIDHERE is the version ID value from the error. Using “301i0000000LyvR” from the error above, open the URL https://…salesforce.com/designer/designer.apexp#Id=301i0000000LyvR. This opens the flow designer with either the process builder or flow that’s causing the issue. Yes it will open a process builder in the flow designer so beware that the culprit may be a process builder and not a flow.
Many thanks to Dakota Walker pointing this tip out in the Which Flow For Version Id Salesforce Forum Question.
What other tips do you have for troubleshooting Flow and Process Builder errors?