Loading

Salesforce Field Service Dispatcher Console Not Loading

Publish Date: Jun 1, 2026
Description

In Salesforce Field Service (FSL), dispatchers may see the error 'Oh boy! Something went wrong' when opening the Dispatcher Console (Field Service tab). This error typically occurs for one of two reasons: (1) the dispatcher user is missing required FSL permission sets, or (2) the Dispatcher Console is attempting to load more data than the Apex CPU timeout limit allows.

Resolution

An error with the Field Service Dispatcher console noting "Oh boy! Something went wrong" can occur for one or more of the following reasons:

1. The affected user does not have the required permissions.


To resolve the issue, assign the affected user both the "FSL Dispatcher License" and "FSL Dispatcher Permissions" permission sets and verify these permission sets are up-to-date.

2. The Field Service Lightning (FSL) app hit the Apex CPU timeout limit.
 
To resolve the issue, limit the amount of data loaded. Gantt loading CPU time is affected by the following parameters:

- Total number of Service Resources
- Total number of Service Territories
- Total number of loaded Service Territory Members
- Total Service Appointments loaded on the Gantt
- Additional Service Appointments loaded on the Service List
- Resource Absences
- Service Resource Capacities
- Service Crew Members
- Number of days loaded on the Gantt
The Gantt will load one day before and after the selected time domain (i.e. for a 1-day view, 3 days will be loaded in the background).
- Number of fields in the Service Appointment and Service Resource Field Sets

The easiest way to reduce the amount of data loaded is to reduce the number of selected Service Territories. As affected Dispatchers can no longer edit the selected Service Territories from the Dispatcher Console, create a custom tab for the User Setting object. This object stores the specific settings that Dispatchers have configured for themselves. By making this tab available to users, they can effectively 'reset' their Dispatcher Console settings:
 
When the tab is available, dispatchers can do the following when they hit the error:
  1. Go to the User Settings tab
  2. Find and select the User Setting record where they are listed as the Owner
  3. Scroll down to the Territories related list (if not available, check the Related tab)
  4. Delete User Setting Territories (click the Del link next to each record in the related list)

By doing the above, users have reset the number of Service Territories loaded in the Dispatcher Console. The next time they navigate to the Field Service tab, they will be prompted to select Service Territories to load. Have them select at most one Service Territory to start. If they continue to see the error, please log a case with Salesforce Support and indicate the affected user as well as the Service Territory they selected.
Knowledge Article Number

000384506

 
Loading
Salesforce Help | Article