0

We use Process Builder to update records. I'm getting this error for the mass update:

UPDATE --- UPDATE FAILED --- ERRORI: (CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY) ITA_IFM_Case_Trigger: System.LimitException: Apex CPU time limit exceeded

Could someone tell me the limitation of update record via Process Builder?

Improve this question
1
  • Process builder is SLOW when compared to Apex AND it does not have a CPU limit per se. It will exceed the 10 second limit and not fail and the very next thing that happens will fail due to the timeout. The only thing you can do is optimize as best you can and consider using apex instead of PB when you have a lot of packages and code that happen as part of a dml
    – Eric
    Commented Oct 28, 2016 at 0:42

1 Answer 1

Reset to default
3

Flows built via Process Builder do indeed consume more CPU Time than Workflow Rules, which in turn consume more than Apex Triggers. If you are running into timeouts, you should move the logic to one of the more efficient options.

You can take a listen through The Dark Art Of CPU Benchmarking for some more information. See also: Should we use process builder at all? and Are Process Builder workflow rules more likely to violate CPU Time limts than a standard/old workflow rules?

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .