You are performing an operation with a Vicasso application and experience an error similar to the following: 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 301XXXXXXXXXXXX

This error typically indicates that there is a custom Process Builder process / flow in place which is causing interference with the operation your performing.

• In some instances, the error message may indicate the name of the Process Builder process / flow which had failed, and sometimes the error will provide an in-depth explanation as to why the automation failed.

 

• If the error message is somewhat limited, but does include "A flow trigger failed to execute the flow with version ID 301XXXXXXXXXXXX", we recommend using the Salesforce Workbench tool linked here to match the ID in the error to the problematic process / flow: https://workbench.developerforce.com/login.php. Once logged into workbench, select Metadata Types and Components from the Jump to menu, click Select, and then choose Flow from the drop down menu on the following page. Next, click Expand All, click Control-F on your keyboard, and enter the Id from the error message. From here you should be able to locate the process / flow which was causing the interference.

Once you have located the automation which had caused the error, please try temporarily disabling it and re-perform the same actions which lead up to the error in the first place. If the error does not occur on additional attempts after the automation has been deactivated, the error is likely related to the how the automation was constructed.

Please review the following articles for best practices on properly implementing a Process Builder process.

https://medium.com/@apeattie/salesforce-process-builder-best-practices-24e674b2b2b1
https://www.salesforce.com/video/1756610/
http://www.salesforceupdates.com/salesforce-process-builder-best-practices/


Please Note: Due to the nature of local automation, errors caused by custom processes / flows fall out of scope for Vicasso application support. For further assistance, please contact your Salesforce administrator or Salesforce implementation partner.