[SalesForce] Callout Limits for future methods and queueable apex

I'm aware from the docs that

"A single Apex transaction can make a maximum of 100 callouts to an HTTP request or an API call."

Is anyone aware if that limit is higher in a future methods or queueable apex? Generally, limits are relaxed in an asynchronous context with apex, but I can't find anything talking about callout limits specifically.

I need to make this callout from a trigger, so it looks like future or queueables are my only options.

Best Answer

I quickly wrote a class with future method to test this behaviour.

public class FutureClassLimitsTest {

    @future(callout=true)
    public static void docallouts(){

        for(Integer i=0;i<200;i++){
            Http http=new Http();
            HttpRequest hr=new HttpRequest();
            hr.setMethod('POST');
            hr.setEndpoint('https://google.com');
            http.send(hr);
        }


    }

}

This is the error I get.

First error: Too many callouts: 101.

So I believe this is uniform for the whole platform irrespective of the transaction(Sync or Async).

Is there a workaround?

Well unless there is a strong business requirement it is kinda bad doing so many callous in a transaction.

We can call a Queauble Method from Queueable method,.. and you can chain them infinitely. Thus using proper implementation you can have 100+ callouts. Batch is another way to tackle this. You have to write /modify data model add a some queue custom SOBJECT to handle your problem.

No limit is enforced on the depth of chained jobs, which means that you can chain one job to another job and repeat this process with each new child job to link it to a new child job. For Developer Edition and Trial organizations, the maximum stack depth for chained jobs is 5, which means that you can chain jobs four times and the maximum number of jobs in the chain is 5, including the initial parent queueable job.

Source: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_queueing_jobs.htm

Related Solutions

[SalesForce] Governor Limits for Asynchronous Methods

You can find the governor limits in the Salesforce documentation. They have also seperated synchronous and asynchronous limits. In the case of the SOQL query Limit, asynchronous Apex has a limit of 200 queries.

See: https://www.salesforce.com/us/developer/docs/apexcode/Content/apex_gov_limits.htm

[SalesForce] Governor Limits on System.enqueueJob in Asynchronous Apex – Documentation Wrong

Yes, the documentation in question is incorrect. You can prove that the Limits class does not conform to what is written therein fairly easily:

public class Demo implements Queueable
{
    public void execute(QueueableContext context)
    {
        system.assertEquals(1, Limits.getLimitQueueableJobs());
    }
    @future
    public static void doStuff()
    {
        system.assertEquals(1, Limits.getLimitQueueableJobs());
    }
}

Proving it for batches is a fairly straightforward alteration of the above.

Some pieces of the documentation, however, do touch on this point in a way that properly explains the governor limits involved. They are somewhat lacking in clarity, but you can only execute one job from within a job. Here's one such example:

Chaining Jobs

If you need to run a job after some other processing is done first by another job, you can chain queueable jobs. To chain a job to another job, submit the second job from the execute() method of your queueable class. You can add only one job from an executing job, which means that only one child job can exist for each parent job. For example, if you have a second class called SecondJob that implements the Queueable interface, you can add this class to the queue in the execute() method as follows:
public class AsyncExecutionExample implements Queueable {
    public void execute(QueueableContext context) {
        // Your processing logic here       

        // Chain this job to next job by submitting the next job
        System.enqueueJob(new SecondJob());
    }
}

Also from the same document:

When chaining jobs, you can add only one job from an executing job with System.enqueueJob, which means that only one child job can exist for each parent queueable job. Starting multiple child jobs from the same queueable job isn’t supported.

Best Answer

Related Solutions

[SalesForce] Governor Limits for Asynchronous Methods

[SalesForce] Governor Limits on System.enqueueJob in Asynchronous Apex – Documentation Wrong

Chaining Jobs

Related Topic