shows how the Salesforce Platform's Flow Control mechanism prevents one org from flooding the batch Apex message type. Prior to adding new entries to the Batch Apex queue, the framework sees that all of the existing entries are associated with Org 1, which also has entries in worker threads (Org 1). It then moves entries from Org 1 to the back of the queue and prioritizes entries form Org 2.