You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the generic Flow error is encountered, add a "View Offending Process Builder or Flow" link that lets one open the process builder or flow that caused the error. The link would be dynamically generated using the version ID found within the error message.
Background
When inserting or updating a record, some times you'll get a Visual Workflow aka Flow generic error message like the following:
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: 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.
Turns out that the Flow Version Id can be used to open the offending Flow or Process Builder even though when you try to open that record id directly, you get an "Insufficient Privileges" error. This Blog Post describes how to determine the offender by opening a special link using the version ID.
The text was updated successfully, but these errors were encountered:
Request
When the generic Flow error is encountered, add a "View Offending Process Builder or Flow" link that lets one open the process builder or flow that caused the error. The link would be dynamically generated using the version ID found within the error message.
Background
When inserting or updating a record, some times you'll get a Visual Workflow aka Flow generic error message like the following:
Turns out that the Flow Version Id can be used to open the offending Flow or Process Builder even though when you try to open that record id directly, you get an "Insufficient Privileges" error. This Blog Post describes how to determine the offender by opening a special link using the version ID.
The text was updated successfully, but these errors were encountered: