function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
sunny.samuel1.3976026459242517E12sunny.samuel1.3976026459242517E12 

Performance issue with one of our Sandbox: taking a longer time for batch polling.

The issue we are seeing is lag time between when a batch is fired versus when it receives resources. In some cases the batch fires at XX:30 but doesn’t actually receive resources to finish for 22 minutes. We see lag time in the future handler as well, a user clicks save and the future handler doesn’t fire for 10+ minutes. The evidence of this is in the log files.
Aakaash NairAakaash Nair
Hi Sunny,

Per the Salesforce architecture batch jobs and Future handler are Asynchronous process and no SLA is provided for the same.

Jobs will be dequeued and processed when resources are available, so if there is a spike of jobs submitted by other orgs in the same db node, it will take a bit longer for their jobs to be processed.

While Salesforce.com make every effort to ensure the app servers can provide a fast turnaround, at times requests will wait a bit longer to be dequeued and processed.

If this is part of a critical process that affects the Org please try to use synchronous processing (e.g. regular SOAP/REST API).

If you still feel the job takes long to execute then you could have the Salesforce.com Support look into this.

Hope the helps!

Please mark this as a best answer if your query  is resolved so others also get help from this thread in future.

Thanks,
Aakaash