What Are Apex Batch Action Results?

Question

What Are “Apex Batch Action Results” in the Spring ’25 Release Updates, and How Can They Be Used?

While reviewing the Spring ’25 release updates for my Salesforce org, I came across a mention of “Apex batch action results.” However, I couldn’t find detailed information about this feature online.

Could someone help explain what Apex batch action results mean? If possible, please share any sample code or use cases that demonstrate how this feature works.

Keywords: Apex, batch, release updates, Spring ’25, action results.

Answer:

When working with Apex batch processing in Salesforce, you might encounter scenarios where you need to handle and process multiple records asynchronously. One of the key components of batch processing in Apex is handling the results of these batch actions. In Salesforce, the term “Apex batch action results” refers to the outcome of batch jobs, specifically the results generated after executing the batch logic. These results might include the success or failure of individual operations (like insertions, updates, or deletions) or any exceptions that were thrown during execution.

The “Request Order” aspect comes into play when you want to maintain or control the sequence in which the batch actions are processed and sorted in relation to their execution. It might be useful in scenarios where the order of execution or result processing is important, such as when you need to keep track of record IDs or ensure that related records are processed in a particular order.

Salesforce doesn’t directly offer an out-of-the-box feature to sort batch action results by request order. However, you can manually sort the results by using custom logic in your execute() method or by utilizing a custom object or a list to track the original request order of the records.

Here’s an example of how you could structure your batch class to track and sort the results by the request order:

public class BatchActionExample implements Database.Batchable<SObject> {
    public String query;

    public BatchActionExample(String q) {
        query = q;
    }

    public Database.QueryLocator start(Database.BatchableContext BC) {
        return Database.getQueryLocator(query);
    }

    public void execute(Database.BatchableContext BC, List<SObject> scope) {
        // Example list to track records by their request order
        List<BatchResult> results = new List<BatchResult>();

        for (SObject record : scope) {
            // Process the record
            try {
                // Your logic here (e.g., update, delete)
                update record;
                results.add(new BatchResult(record.Id, 'Success'));
            } catch (Exception e) {
                results.add(new BatchResult(record.Id, 'Failed', e.getMessage()));
            }
        }

        // Now, sort the results by request order
        results.sort((r1, r2) -> r1.requestOrder.compareTo(r2.requestOrder));

        // Process the sorted results (you can log, notify, or take further actions)
        for (BatchResult result : results) {
            System.debug('Record ' + result.recordId + ' processed with status ' + result.status);
        }
    }

    public void finish(Database.BatchableContext BC) {
        // Final processing after the batch has been completed
    }

    public class BatchResult {
        public String recordId;
        public String status;
        public String errorMessage;
        public Integer requestOrder;

        public BatchResult(String id, String status, String errorMessage = null) {
            this.recordId = id;
            this.status = status;
            this.errorMessage = errorMessage;
            this.requestOrder = Integer.valueOf(recordId); // Example logic for tracking order
        }
    }
}

Explanation:

1. The BatchActionExample class implements the Database.Batchable interface and processes a list of records (SObjects).
2. In the execute() method, a custom class BatchResult is used to track each record’s ID, status, and any error message, along with a requestOrder to keep track of the order.
3. After processing the batch, the results are sorted by the requestOrder field using a custom sorting mechanism.
4. Finally, you can use the sorted results to perform additional processing or logging as needed.

By sorting the results manually as shown, you can control the processing order based on your own tracking logic. This is essential when the request order impacts downstream operations, such as related record processing or when specific sequencing is necessary.

Enroll for Career-Building Salesforce Training

Our Salesforce Course delivers an all-encompassing learning experience, crafted to help you gain mastery over the Salesforce platform and pave the way for a successful career. Whether you aspire to become a Salesforce Administrator, Developer, or work on AI integrations, our courses delve into every essential aspect of the platform. With an emphasis on practical application through real-world projects, our training ensures you build hands-on expertise and can address real business challenges effectively. Guided by experienced industry professionals, our program equips you with the knowledge and confidence to thrive in the Salesforce ecosystem.

In addition to comprehensive technical training, our Salesforce training in India provides exceptional career development support. This includes personalized mentorship and expert advice to help you prepare for certifications. From in-depth learning materials to real-time project work and targeted interview coaching, we ensure you’re fully prepared for the job market. Our ultimate goal is to not only strengthen your Salesforce proficiency but also to position you for success in your next role. By completing the program, you’ll acquire the skills, experience, and confidence needed to excel in Salesforce and advance your career.