Loading

Understanding the Account Engagement Managed Apex Class ScheduledDispatcher Job

Дата публикации: Sep 30, 2025
Решение
ScheduledDispatcher is often related to Scoring Categories in Salesforce. When a record is updated, the ScheduledDispatcher is created. When the update is executed, the ScheduledDispatcher is "aborted." The aborted status is actually an indication the process is working as expected. 

Apart from the lead / contact update on scoring categories, it’s also responsible for helping to clean up old ObjectChangeLog records. 

AsyncRequestBatchProcessor works with ScheduledDispatcher to clean up old ObjectChangeLog records as well as helps sync Scoring Category information between Account Engagement and Salesforce. 

So, these two Apex jobs often work in tandem. 

If the ScheduledDispatcher entries are queued and not aborted, there could be an issue that may need further investigating.

Two additional points which might be worth bearing in mind when investigating:

  1. The main cause of a large amount of jobs in 'queued' status is that the Salesforce governor limits around concurrent scheduled Apex jobs is being hit (ie the jobs are backlogged and can't complete). Org limits are described here: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_gov_limits.htm
  2. Apart from the lead / contact update on scoring categories, the other main job that calls that class is the oclPruningBatch job which is the job we use to delete ObjectChangeLogs from the customer org that have gone 3 weeks without being used.
Log a support case if you need additional help with troubleshooting 'queued' entries.

If you don't use scoring categories, the ScheduledDispatcher Apex class is safe to disable. 
Номер статьи базы знаний

000383416

 
Загрузка
Salesforce Help | Article