Loading

Description of Asynchronous processing in Salesforce

Date de publication: Jun 14, 2026
Description

Asynchronous processes are requests that do not execute immediately at the time they are submitted, but instead execute separately, one at a time from a queue. In computing, a message queue stores all requests from different systems to ensure each request is processed in the order received. Salesforce uses the same queue-based asynchronous processing architecture. Each asynchronous request is placed in the queue, stored for recovery reasons, and de-queued for execution across multiple organizations within each instance. Because many customers share available resources on each Salesforce instance, the exact execution timing of asynchronous requests cannot be predicted or guaranteed.

 

Résolution

No SLA for Asynchronous Processing

There is no Service Level Agreement (SLA) for when an asynchronous process will execute or finish. The number of requests queued varies across organizations on each Salesforce instance, making timing unpredictable. Salesforce is continuously working to improve asynchronous processing performance.

Examples of Asynchronous Request Types

The following are examples of requests that are processed asynchronously in Salesforce:

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

000384188

 
Chargement
Salesforce Help | Article