Loading

Description of Asynchronous processing in Salesforce

Date de publication: Oct 13, 2022
Description

Let's start first by mentioning what the Asynchronous process is, and how it is used in Salesforce.

Asynchronous processes are requests which do not execute at the same time but execute separately one at a time. In computing, it's common to use a queue to store all the messages sent from different systems to ensure that each request will be processed in the order they were sent. This is called a message queue.

We use the same queue-based asynchronous processing architecture in Salesforce too. Each asynchronous request is processed first in the queue, stored for recovery reasons, and de-queued for execution in multiple organizations within each instance. The timing of when the execution will start or finish is hard to predict because of the fact that the number of requests queued can vary for organizations on each instance.
 
Résolution

Due to the above reasons and the fact that many customers are sharing the available resources, there is no SLA for asynchronous process as to when it will execute or finish. We are always looking for ways to improve this behavior. Examples of these types of requests including:

  • Scheduled Reports
  • Dashboard refreshes
  • PackageUploadRequest
  • Future Methods
  • Batch Apex
  • Queueable Apex
  • Bulk API
  • PackageVersionCreation
  • Deployments
  • Running Apex tests in deployments/PackageVersionCreation
Numéro d’article de la base de connaissances

000384188

 
Chargement
Salesforce Help | Article