Apex CPU Limit Error : after running into an Apex CPU limit error whether anything is committed to the database

In a batch that updates an object that then activates a trigger, 
would it stop at the object level or at the trigger level or does it depend on 
when the apex limit is hit?

Any governor limit, including Apex CPU timeouts, reverts all changes to the database for the entire transaction. That means no records are created, updated, deleted, undeleted, merged, converted, etc. The only exception to this rule is that any logs that are enabled will be preserved (in Setup > Monitoring > Debug Logs). 
In the case of a batch, if it occurs in the start method, the entire batch is aborted, while '
if it occurs during an execute function, only that single batch is aborted (but prior batches are already committed, and future batches may still successfully commit), and 
in the finish method, a governor limit would prevent chaining calls, sending emails, etc.

Comments

Popular posts from this blog

All about workflow rule , limitation and important points with example

Custom Setting in Salesforce

Action tags in VisualForce Salesforce