Salesforce Stack Exchange is a question and answer site for Salesforce administrators, implementation experts, developers and anybody in-between. It only takes a minute to sign up.
Sign up to join this community
I've seen the following values in the AsyncApexJob table during the 'cradle to grave' life cycle of a Batch Apex job:
BEFORE running:
WHILE running:
AFTER running:
But I've noticed an additional picklist value that I've never encountered in the wild: Holding. Does anyone have experience with this? Do I need to include this when determining if a batch is running?
Based on the Summer '14 Release Notes the holding status appears to be associated with the new Apex Flex Queue feature.
The Apex Flex Queue pilot enables you to submit batch jobs beyond the allowed limit of five queued or active jobs. Any jobs that are submitted for execution but aren’t processed immediately by the system are in holding status and are placed in a separate queue (the Apex flex queue). Up to 100 batch jobs can be in the holding status. When system resources become available, the system picks up jobs from the Apex flex queue and moves them to the batch job queue. The status of these moved jobs changes from Holding to Queued. Queued jobs get executed when the system is ready to process new jobs.
Without administrator intervention, jobs are processed first-in first-out—in the order in which they’re submitted. Administrators can modify the order of jobs that are held in the Apex flex queue to control when they get processed by the system. For example, you can move a batch job up to the first position in the holding queue so that it is the first job that gets processed when the system fetches the next held job from the flex queue.
The Holding status is mentioned in the Summer 14 release notes under the new pilot feature of "Submit More Batch Jobs with Apex Flex Queue". Summer 14 release site: salesforce.com/customer-resources/releases/summer14.
