2

When editing a record, I am getting the below error:

The record couldn’t be saved because it failed to trigger a flow. A flow trigger failed to execute the flow with version ID 301w0000000Gufm. 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.

But interestingly, this flow doesn't show up in my flow list: enter image description here

Note I have only one flow here in all flows view. And it is not the flow I am looking for.

Aside from it, I can open the flow by directly putting the id into the url: https://eu3.salesforce.com/designer/designer.apexp#Id=301w0000000Gufm

But I am wondering why I am unable to see that flow in my list. I am an administrator so it is a little bit weird.

  • 301 is the flow version, so maybe it's within that flow? I've also gotten that error when the flow was trying to do something but when it edited a record it kicked off a workflow update that failed so the flow failed. – Dan Wooding Sep 8 '17 at 2:33
  • @DanWooding I have checked the version and name. The flow name is different. – Lance Shi Sep 8 '17 at 3:15
  • 5
    Process Builder are also a type of Flow (they report as Flow errors when Things Go Wrong). Do you have any active Process Builders on the object(s) in question? – sfdcfox Sep 8 '17 at 4:17
  • @sfdcfox It is a process builder. Thanks a lot for that! – Lance Shi Sep 8 '17 at 6:13
4

Flows and Process Builder both use the same underlying engine to perform, and therefore suffer from similar limitations, like consuming CPU governor limits. This shared engine is what makes it possible (from a technology standpoint) for Process Builder to call Flows and @InvocableMethod Apex Code. Instead of reinventing the wheel, they simply repurposed it. Both the on-screen errors and the errors emailed to administrators will call a Process Builder a Flow, and have similar characteristics that makes it (probably) impossible to tell the difference between the two. So, whenever you encounter this error, administrators should check the Process Builder page as well as the Flow page, since the error could have come from either area.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.