[SalesForce] Flow exception, but flow is not visible in setup

I encounter Flow error when trying to Insert record in test class:

System.DmlException: Insert failed. 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 3010E000000CpxD. 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.: []

I wanted to add fault message, so I can see what is the deal, but its not displayed in setup in flows tab and I can't add in process builder either.
I managed to view it in Flow Designer. But I still can't find where it's invoked from.

I haven't worked much with flows, so maybe it's a silly question, but why I can't see it in setup? To my knowledge there is no Record Sharing for flows.

UPDATE

Here is the not accessible flow

Here are visible flows

And here is list of processes in Process builder (I sorted by type and there is no Contact)

Interesting part is that I was able to find this flow in process builder in another related org.

Best Answer

This article from the Salesforce Knowlegebase may help: https://help.salesforce.com/articleView?id=000231232&language=en_US&type=1

Related Solutions

[SalesForce] How to debug flow errors

When you see any flow error you can follow below steps:

Identify flow name: You can identify flow name by id using workbench from metadata type and component.

When there is flow error salesforce send an email to the last modified person with detailed information where flow failed. It contains every single step of flow and at what steps it failed.

As a flow best practice, Salesforce recommend configuring the fault connectors in your flow so that you always receive an email when a flow fails. In the email, include the current values of all your flow’s resources. The resource values can give you insight into why the flow failed.

[SalesForce] How to avoid validation rule contradicting the process builder

Validation rules apply any time a record is altered, whether that alteration takes place in Process Builder, the user interface, or the API. You can't intercept the validation rule's message and allow the update to complete successfully.

In a Process Builder or Flow context, one tactic you can use to allow an un-validated change to go through if and only if it's made via a specific automation is to build a check into your rule for a hidden field (not shown on any page layout, or hidden from users via FLS).

Say we have a Checkbox field Process_Builder_Update__c. Set this to true prior to making your updates. Then, in your validation rule, add a check for this field so that the rule does not evaluate to true when the field is set:

AND(NOT(Process_Builder_Update__c), EXISTING_VALIDATION_RULE)

Then, the validation rule won't go off when your process makes its updates, because it sets Process_Builder_Update__c, but it will still be in effect when your users make changes.

You'll also want to un-set the flag once you're finished, so that users can't bypass the validation rule with the flag still set. Your flow should finish by setting the field back to false.

This won't work if your flow leaves your records in an un-validatable state (where any change will fail the validation rule), because unsetting the field will fail. However, you really won't want to leave your records like that anyway, as it means any user update will fail.

Related Topic

[SalesForce] How to debug a flow as a specific user