Loading

FSL Dynamic Scaling: Global Optimization Fails Beyond 5,000 Records When Service Territory ESO Setting Is Disabled

게시 일자: Jun 22, 2026
상세 설명

Symptom

  • Global Optimization stops processing are above 5000 records.
  • The optimization request fails or does not scale beyond the standard limit.
  • ESO and Dynamic Scaling appear enabled in org-wide settings, but the issue persists.
  • Field Service Technician schedules are not fully optimized, impacting customer commitments.

Cause

Dynamic Scaling requires ESO to be enabled both at the org level and at the individual Service Territory level. Even if ESO is enabled org-wide, each Service Territory used in an Optimization Request must also have the Use Enhanced Scheduling and Optimization field explicitly set to true.


If this field is set to false (or left unchecked) on the Service Territory record associated with the Optimization Request, Dynamic Scaling will not activate and Global Optimization will be capped at the standard record limit.

 

솔루션

Follow these steps to resolve Global Optimization failures caused by a disabled ESO setting on the Service Territory:

  1. Identify the Optimization Request that failed and note the associated Service Territory.
    1. Navigate to the Optimization Request record and check the Service Territory field.
  2. Open the associated Service Territory record.
  3. Locate the Use Enhanced Scheduling and Optimization field on the Service Territory.
  4. Verify that this field is set to true (enabled).
    1. If it shows false, enable it by editing the record.
  5. Save the Service Territory record.
  6. Re-run the Global Optimization request.
  7. Confirm that optimization now processes beyond 5,000 records successfully.
추가 자원

Key Documentation: Dynamic Scaling is available only when you're using Enhanced Scheduling and Optimization. Reference: Enable Dynamic Scaling for Enhanced Scheduling and Optimization

Knowledge 기사 번호

005386960

 
로드 중
Salesforce Help | Article