What are Apex Future Methods?<\/h2>\n\n\n\n
Apex Future Methods are static methods marked @future that Salesforce queues and runs later. They must return void, and their parameters must be primitive types, such as Id, String or Integer, or collections of them. When you call one, the call returns at once, and the work happens after the current transaction commits.<\/p>\n\n\n\n
Think of dropping a letter in a post box. You do not wait at the box until it arrives. You also cannot put a parcel with fragile items in it, only a flat envelope. Future methods are that post box: quick, simple, and limited in what they carry.<\/p>\n\n\n\n
Why Apex Future Methods Matter<\/h2>\n\n\n\n
Some small tasks cannot run in the current transaction. Here is why Apex Future Methods matter at Bright Path Tutors.<\/p>\n\n\n\n
- \n
- First, a trigger must notify a partner system, but triggers cannot make callouts.<\/li>\n\n
- Also, activating a tutor’s user record while updating a course causes a mixed DML error.<\/li>\n\n
- Next, some slow calculations should not delay the user’s save.<\/li>\n\n
- Future methods need no extra class, just one annotation.<\/li>\n\n
- Finally, a lot of existing code uses them, so you must understand them.<\/li>\n<\/ul>\n\n\n\n
So Apex Future Methods are a quick fix for simple background work.<\/p>\n\n\n\n
How Apex Future Methods Work<\/h2>\n\n\n\n
Apex Future Methods follow a short flow. First, synchronous code calls the static @future method with primitive values, often record Ids. Next, Salesforce stores the request and the call returns at once. Then the current transaction finishes and commits. After that, the future method runs in a new transaction with async limits. Finally, it queries fresh data using the Ids, does its work, and ends without returning anything.<\/p>\n\n\n\n
![\"Apex](\"https:\/\/swapnilzambare.com\/blog\/wp-content\/uploads\/2026\/11\/apex-future-methods-explained-diagram-1-1024x640.png\")
How a future method runs after the transaction commits.<\/figcaption><\/figure>\n\n\n\n The @future Annotation<\/h3>\n\n\n\n
Mark a public or private static void method with @future. The method cannot return a value, because the caller has already moved on.<\/p>\n\n\n\n
Primitive Parameters Only<\/h3>\n\n\n\n
Parameters must be primitives, arrays of primitives, or collections of primitives. You cannot pass sObjects, because the record might change before the method runs. So pass Ids and query the records inside.<\/p>\n\n\n\n
callout=true<\/h3>\n\n\n\n
Add @future(callout=true) when the method calls another system over HTTP. Without it, callouts are not allowed.<\/p>\n\n\n\n
Limits and Rules<\/h3>\n\n\n\n
You can call up to 50 future methods in one transaction. Also, you cannot call a future method from another future method or from Batch Apex. Finally, the order in which future methods run is not guaranteed.<\/p>\n\n\n\n
Apex Future Methods Rules at a Glance<\/h2>\n\n\n\n
The table below sums up the main rules.<\/p>\n\n\n\n
Rule<\/th> Detail<\/th><\/tr><\/thead> Method type<\/td> static, returns void<\/td><\/tr> Parameters<\/td> Primitives or collections of primitives<\/td><\/tr> Callouts<\/td> Only with @future(callout=true)<\/td><\/tr> Calls per transaction<\/td> Up to 50<\/td><\/tr> Called from future or batch<\/td> Not allowed<\/td><\/tr> Job Id returned<\/td> No<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Future Methods vs Queueable Apex<\/h2>\n\n\n\n
The table below compares future methods with Queueable Apex.<\/p>\n\n\n\n
Feature<\/th> Future method<\/th> Queueable Apex<\/th><\/tr><\/thead> Parameters<\/td> Primitives only<\/td> Any type, including sObjects<\/td><\/tr> Job Id to track<\/td> No<\/td> Yes<\/td><\/tr> Chaining<\/td> Not possible<\/td> One child job per job<\/td><\/tr> Code needed<\/td> One annotation<\/td> A class with execute<\/td><\/tr> Best for<\/td> Small, simple tasks<\/td> Most new async work<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n When to use which is simple. Use a future method for a tiny, one-off callout or mixed DML fix. Use Queueable for anything you need to track, chain or pass complex data to.<\/p>\n\n\n\n
![\"Apex](\"https:\/\/swapnilzambare.com\/blog\/wp-content\/uploads\/2026\/11\/apex-future-methods-explained-diagram-2-1024x640.png\")
Future method vs Queueable Apex.<\/figcaption><\/figure>\n\n\n\n A Real Apex Future Methods Example<\/h2>\n\n\n\n
Let’s use Apex Future Methods for two common jobs at Bright Path Tutors.<\/p>\n\n\n\n
Step 1: Fix a Mixed DML Error<\/h3>\n\n\n\n
public with sharing class TutorAccessService {\n\n \/\/ Called after a course update; user changes need their own transaction\n @future\n public static void activateTutors(Set<Id> userIds) {\n List<User> tutors = [SELECT Id, IsActive FROM User WHERE Id IN :userIds];\n for (User u : tutors) {\n u.IsActive = true;\n }\n update tutors;\n }\n}<\/code><\/pre>\n\n\n\nUpdating a setup object, such as User, and a normal object, such as Course__c, in one transaction causes a mixed DML error. So the course logic calls activateTutors with the user Ids, and the user update runs later in a separate transaction.<\/p>\n\n\n\n
Step 2: Make a Callout from a Trigger<\/h3>\n\n\n\n
public with sharing class PartnerNotifier {\n\n @future(callout=true)\n public static void notifyNewCourses(Set<Id> courseIds) {\n for (Course__c c : [SELECT Id, Name, Fee__c FROM Course__c WHERE Id IN :courseIds]) {\n HttpRequest req = new HttpRequest();\n req.setEndpoint('callout:Partner_Catalog\/courses');\n req.setMethod('POST');\n req.setBody(JSON.serialize(c));\n HttpResponse res = new Http().send(req);\n System.debug(c.Name + ' sent, status ' + res.getStatusCode());\n }\n }\n}<\/code><\/pre>\n\n\n\nThe trigger handler calls notifyNewCourses with all new course Ids at once. Because of callout=true, the method can send HTTP requests. It queries the courses fresh, so it sends the saved values.<\/p>\n\n\n\n
Step 3: Call It Once per Transaction<\/h3>\n\n\n\n
when AFTER_INSERT {\n PartnerNotifier.notifyNewCourses(Trigger.newMap.keySet());\n}<\/code><\/pre>\n\n\n\nWith Apex Future Methods, one call handles every course in the batch. So a Data Loader import of 200 courses uses one future call, not 200.<\/p>\n\n\n\n
Step 4: Check the Log<\/h3>\n\n\n\n
Here is a simplified debug log from the future method’s transaction.<\/p>\n\n\n\n
CODE_UNIT_STARTED|PartnerNotifier.notifyNewCourses\nUSER_DEBUG|Apex Basics sent, status 201\nUSER_DEBUG|SOQL Basics sent, status 201<\/code><\/pre>\n\n\n\nThe log appears as a separate entry, because the future method runs in its own transaction after the save.<\/p>\n\n\n\n
Testing Apex Future Methods<\/h2>\n\n\n\n
Call the code that triggers the future method between Test.startTest and Test.stopTest. Then the future method runs at stopTest, before your asserts. For callouts, also set a mock with Test.setMock first.<\/p>\n\n\n\n
Common Mistakes with Apex Future Methods<\/h2>\n\n\n\n
- \n
- Calling a future method inside a loop, once per record.<\/li>\n\n
- Trying to pass sObjects as parameters.<\/li>\n\n
- Calling a future method from Batch Apex or another future method.<\/li>\n\n
- Forgetting callout=true for HTTP calls.<\/li>\n\n
- Relying on the order in which future methods run.<\/li>\n<\/ul>\n\n\n\n
Best Practices for Apex Future Methods<\/h2>\n\n\n\n
- \n
- Pass a Set of Ids and query fresh data inside the method.<\/li>\n\n
- Call each future method once per transaction with all records.<\/li>\n\n
- Check System.isFuture() or System.isBatch() before calling, to avoid errors.<\/li>\n\n
- Prefer Queueable for new code that needs tracking or chaining.<\/li>\n\n
- Always test with Test.startTest and Test.stopTest.<\/li>\n<\/ul>\n\n\n\n
Practice Task<\/h2>\n\n\n\n
Write a guard that calls PartnerNotifier.notifyNewCourses only when the code is not already running in a future or batch context. Hint: use System.isFuture() and System.isBatch().<\/p>\n\n\n\n
Most Asked Interview Questions on Apex Future Methods<\/h2>\n\n\n\n
Future methods are a classic interview topic. Here are the 21 questions asked most about Apex Future Methods.<\/p>\n\n\n\n
Basic Questions on Apex Future Methods<\/h3>\n\n\n\n
Q1: What is a future method?<\/strong><\/p>\n\n\n\n
A static void method marked @future that Salesforce runs later in its own transaction.<\/p>\n\n\n\n
Q2: What return type must a future method have?<\/strong><\/p>\n\n\n\n
void.<\/p>\n\n\n\n
Q3: Why must future methods be static?<\/strong><\/p>\n\n\n\n
Because they run in a new transaction with no object instance from the caller.<\/p>\n\n\n\n
Q4: What parameter types are allowed?<\/strong><\/p>\n\n\n\n
Primitives, arrays of primitives, and collections of primitives.<\/p>\n\n\n\n
Q5: Why can’t you pass sObjects?<\/strong><\/p>\n\n\n\n
The record could change before the method runs, so you pass Ids and query fresh data.<\/p>\n\n\n\n
Q6: How do you allow callouts in a future method?<\/strong><\/p>\n\n\n\n
Use @future(callout=true).<\/p>\n\n\n\n
Q7: How many future calls are allowed per transaction?<\/strong><\/p>\n\n\n\n
Up to 50.<\/p>\n\n\n\n
Code and Scenario Questions on Apex Future Methods<\/h3>\n\n\n\n
Q8: Can you call a future method from a batch class?<\/strong><\/p>\n\n\n\n
No.<\/p>\n\n\n\n
Q9: Can a future method call another future method?<\/strong><\/p>\n\n\n\n
No.<\/p>\n\n\n\n
Q10: How do you fix a mixed DML error with a future method?<\/strong><\/p>\n\n\n\n
Move the setup object DML, such as user updates, into a future method.<\/p>\n\n\n\n
Q11: How do you get the result of a future method?<\/strong><\/p>\n\n\n\n
You cannot directly. It returns nothing and gives no job Id, so check the data it changed.<\/p>\n\n\n\n
Q12: How do you test a future method?<\/strong><\/p>\n\n\n\n
Call it between Test.startTest and Test.stopTest, then assert after stopTest.<\/p>\n\n\n\n
Q13: How do you avoid calling a future method from a future context?<\/strong><\/p>\n\n\n\n
Check System.isFuture() before calling it.<\/p>\n\n\n\n
Q14: Do future methods run in a set order?<\/strong><\/p>\n\n\n\n
No. Order is not guaranteed.<\/p>\n\n\n\n
Advanced Questions on Apex Future Methods<\/h3>\n\n\n\n
Q15: Why is Queueable often better than future?<\/strong><\/p>\n\n\n\n
It accepts complex types, returns a job Id, supports chaining and finalizers.<\/p>\n\n\n\n
Q16: Can a future method be called from a Visualforce constructor?<\/strong><\/p>\n\n\n\n
No. Future methods cannot be used in Visualforce getters, setters or constructors.<\/p>\n\n\n\n
Q17: How do you pass complex data to a future method?<\/strong><\/p>\n\n\n\n
Serialize it to a JSON string, then deserialize it inside the method, or switch to Queueable.<\/p>\n\n\n\n
Q18: Do future methods count toward the daily async limit?<\/strong><\/p>\n\n\n\n
Yes. They share the org’s daily asynchronous execution allowance.<\/p>\n\n\n\n
Q19: What happens if a future method fails?<\/strong><\/p>\n\n\n\n
Its changes roll back and the error appears in Setup > Apex Jobs.<\/p>\n\n\n\n
Q20: Which limits apply inside a future method?<\/strong><\/p>\n\n\n\n
Asynchronous limits, such as 200 SOQL queries and 12 MB heap.<\/p>\n\n\n\n
Q21: When would you still choose a future method today?<\/strong><\/p>\n\n\n\n
For a tiny, isolated callout or mixed DML fix where tracking is not needed.<\/p>\n\n\n\n
Official Resources<\/h2>\n\n\n\n