Loading
Upcoming Mandatory Changes to Public Key Infrastructure (PKI)Read More
Salesforce Enforces New Security Requirements in Summer 2026Read More

Error "The size of the remote answer exceeds the limit of 15mb" When Loading Dispatcher Console Gantt in Salesforce Field Service

Publish Date: Jul 5, 2026
Description

When opening the Salesforce Field Service Dispatcher Console (Gantt chart), dispatchers encounter the error:

"The size of the remote answer exceeds the limit of 15mb"

The Gantt chart does not load, and dispatchers cannot view or manage Service Appointments. This error may persist even after reducing the time horizon (for example, from weekly to daily) or limiting the number of selected Service Territories.

Symptoms

  • The Dispatcher Console Gantt chart displays the error "The size of the remote answer exceeds the limit of 15mb" and does not render.
  • Reducing the Gantt horizon or deselecting Service Territories does not resolve the error.
  • The issue is reproducible when selecting specific Service Territories that contain anomalous Shift data.
  • Dispatchers are unable to schedule or reassign Service Appointments.

 

Resolution

The Salesforce Field Service Dispatcher Console enforces a 15MB limit on the remote response payload returned per request when loading the Gantt chart. When Shift records within a Service Territory (or its child territories) have EndTime values set abnormally far into the future (for example, 20 or more years ahead), the Gantt attempts to load and render data spanning that entire date range. This causes the response payload to exceed the 15MB threshold, triggering the error.
Potential Causes of Anomalous Shift End Dates

  • Manual data entry errors when creating or editing Shift records.
  • Integration or automation logic that incorrectly calculates EndTime values.
  • Data migration issues that set placeholder dates far in the future.

Steps to Resolve the 15MB Gantt Load Error in Salesforce Field Service

  1. Identify the affected Service Territory. Select Service Territories one at a time in the Dispatcher Console to isolate which territory triggers the error. Check child Service Territories as well.
  2. Review Shift records with end dates set unreasonably far in the future. In the identified Service Territory, query or filter Shift records where the EndTime field is set beyond your operational planning horizon.
  3. Correct the anomalous end dates. Update the EndTime field on the identified Shift records to a reasonable date within your operational planning horizon.
  4. Reload the Dispatcher Console. After correcting the Shift records, reload the Gantt chart. The affected Service Territories now load without error.
  5. Prevent recurrence. Consider adding a Validation Rule on the Shift object to reject EndTime values beyond a defined threshold (for example, 2 years from today). Review any integrations or automations that create Shift records to ensure date calculations are correct.
Knowledge Article Number

005388475

 
Loading
Salesforce Help | Article