Loading

Proactive Alert Monitoring: Dequeue Latency

Publiseringsdato: Jan 26, 2024
Beskrivelse

Salesforce is built on a multi-tenant structure and as such, dequeue times can vary depending on the current load and available resources. All Asynchronous processes are typically run in the background at a later time once resources become available and may be subject to dequeue latency. As asynchronous processes have no SLA, poorly implemented requests can cause performance issues if they become stuck in the queue or run very long.

A Dequeue Latency alert indicates that asynchronous jobs are taking a longer time than usual in the queue before processing by the server. A Dequeue Latency alert will be for one of the following asynchronous job types:

  • Apex Future
  • Apex Queueable
  • Dashboard
  • Bulk API


The MQ Longest Wait Time monitor will track messages that are still in flight but have not yet been dequeued, whilst the Dequeue Latency monitors will alert you when specific features (as listed above) have been dequeued through saw increased time to do so.

Please note there is no SLA for dequeue time.

The Signature Success plan’s Proactive Monitoring product offers multiple monitors to monitor for, and alert you to, sustained increases in dequeue latency or wait times. This article outlines some scenarios to help you investigate should you receive an alert. In addition, on the Salesforce Help site Designated contacts and above can see your realtime metrics, alerts & more.


Causes

Dequeue Latency may occur for a variety of reasons:

  • Large volume of a particular job type in the queue
  • Implementation of Fair Usage Policy
  • Performance Degradation
Løsning


Here are a few suggestions and resources that may help to resolve this error.
 

Large volume of a particular job type in the queue

  • A sudden large volume of jobs of a particular type can cause a temporary backlog in the queue.


Implementation of Fair Usage Policy

  • If an organizations's asynchronous jobs are utilizing a significant amount of resources, some jobs may be held in the queue longer to ensure resources are conserved for other organizations. To prevent this, ensure the Apex code being executed within the Asynchronous job is optimized and executes quickly. Review Apex Best Practices for more information.


Performance Degradation

  • Dequeue Latency can be a result of a performance degradation. These are instance-specific and can be checked here.
 

Additional Resources

Help and Developer Resources:

Knowledge-artikkelnummer

000384169

 
Laster
Salesforce Help | Article