When Not to Run Multiple, Simultaneous Batch Jobs

Do not run multiple, simultaneous batch jobs in the following cases:

  • If multiple assignment batches are executed for the same object.

Note: If multiple assignment batches are executed for the same object using workload criteria, then the results can potentially vary and might not be as desired.
  • If the batch jobs update rows on the same table or tables.

  • If one batch job updates records in a table or tables used by another batch job as input.

  • If the batch jobs use workload criteria to assign the same object.

Examples of when you should not run multiple simultaneous batch jobs include:

  • Contact and Contact Denormalization, because the same tables are updated.

  • Account and Contact Denormalization, because Contact Denormalization uses Account team as input.

  • Opportunity and Contact Denormalization, because Contact Denormalization uses Opportunity team as input.