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.
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.
The following are examples of requests that are processed asynchronously in Salesforce:
000384188

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.