what's the total number of "p"s in:
q: the record couldn’t be saved because it failed to trigger a flow - process builder i have one process builder which helps me to do certain things on my opportunity create/update and all.
now, the problem is i have written one trigger on opportunity which is expected to run "after update" while checking certain conditions and business logic following the same.
check out the following screenshot - for more detailed error message.

any suggestions ? or help ?
i have found following as known issue 1    and known issue 2. this might help to answer.
updated question : 

my trigger is also getting called too many times where i found
  trigger.new() = null

debug logs

08:43:49.437 (5437733373)|exception_thrown|[37]|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 301110000000zde.  contact your administrator
  for help.: []
08:43:49.439 (5439388332)|fatal_error|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 301110000000zde.  contact your administrator
  for help.: []


a: you need to check if the procees builder is getting null values for any field on opportunity [ lookup or any other ]. provide legitimate value; it will work...!
there is always a missing value in process builder which brings this exception.
thanks...!

a: we do get this error while working with flow.for more details you can go to this link:https://success.salesforce.com/issues_view?id=a1p300000008xn7aae
thanks 
himanshu

a: had the same problem recently and decided to leave an answer.
there is a knowledge article about this error is case of a data loader. it basically says:

while process builder is being improved to better handle bulk processing, it can still generate errors when a large data loader insert or upsert triggers a process.

and their resolution is... to set the batch size smaller!

within data loader, navigate to settings>settings and lower the batch size to "1".
this will perform the update in smaller chunks, and allow process builder the timings required to complete the actions.  this will cause only a minimal impact on update times for the data loader process.
note: some environments may support slightly larger batch sizes like "20" without errors but, if the error persist with "20" the batch should be set to "1".


for your case it might be that you are in a loop that where a trigger and the process builder are invoking each other

user
The passage contains 48 "p"s.
assistant