The record couldn’t be saved bese it failed to trigger a flow. A flow trigger faild to execute the flow with version ID 3015800000058CB

  • 1
  • Question
  • Updated 1 year ago
  • Answered
The record couldn’t be saved because it failed to trigger a flow. A flow trigger failed to execute the flow with version ID 3015800000058CB. Flow error messages: This interview has been terminated as another interview in the same bulk execution request failed with the following error: An unhandled fault has occurred in this flowAn unhandled fault has occurred while processing the flow. Please contact your system administrator for more information. Contact your administrator for he
Photo of Matrix

Matrix

  • 590 Points 500 badge 2x thumb

Posted 1 year ago

  • 1
Photo of Matrix

Matrix

  • 590 Points 500 badge 2x thumb
Please help soon
(Edited)
Photo of Matrix

Matrix

  • 590 Points 500 badge 2x thumb
what should i do now?
Photo of Matrix

Matrix

  • 590 Points 500 badge 2x thumb
i cant understand before some time it was fine
Photo of Matrix

Matrix

  • 590 Points 500 badge 2x thumb
Everything is working fine but this message is annoying
Photo of Matrix

Matrix

  • 590 Points 500 badge 2x thumb
Hi Chandra thank you. i deactivate the process builder . and its stops showing message. what have to do if i want to active the process builder and dont want to show error message
Photo of Chandra V

Chandra V, Champion

  • 6,966 Points 5k badge 2x thumb
There is something wrong in the process builder that you need to correct.  I find it most helpful to use the email that the author of the process builder gets as a result of this error.... the email subject looks like this: "Error Occurred During Flow "Your Flow Name": The flow failed to access the..."

At the very bottom of this email, there is usually an Error.  In an example one we had, our process builder was creating a chatter post to a user referenced on the record.  When the flow was triggered (during record save), the referenced user was NULL, so the chatter failed which caused the flow to fail.  The error message in the email helped us figure that out.