Loading

Salesforce Field Service: Dispatcher Console Hangs at "Loading Service Territory Members" Due to Corrupt FSL__FavoriteTerritories__c Value

Veröffentlichungsdatum: Jul 23, 2026
Beschreibung

The Salesforce Field Service Dispatcher Console loads in four sequential stages: Verifying permissions, Loading user settings, Loading service territories and resources, and Loading service territory members. When the Favorite Territories field (FSL__FavoriteTerritories__c) on the Field Service user settings record (FSL__UserSetting__c) contains a corrupt or malformed value, the console hangs indefinitely at Stage 4 without displaying an error message.

Symptoms

  • The Dispatcher Console completes Stages 1 through 3 with green checkmarks.
  • Stage 4, "Loading service territory members," displays a spinner that never completes.
  • No error message appears.
  • The issue persists regardless of the user's profile, including System Administrator.
  • The issue persists in incognito/private browser windows and across different browsers.
  • Other users in the same org with correctly formatted FSL__UserSetting__c records load the Dispatcher Console without issue.
  • Reassigning or recreating permission sets (FSL_Dispatcher_License, FSL_Dispatcher_Permissions) does not resolve the issue.
  • The issue is not limited to the Dispatcher Console — Field Service GO may also hang at the same stage.
Lösung

This section explains how to resolve a Salesforce Field Service Dispatcher Console that hangs indefinitely at Stage 4 ("Loading Service Territory Members") due to a corrupt or malformed value in the Favorite Territories field (FSL__FavoriteTerritories__c) on the user's Field Service user settings record (FSL__UserSetting__c).
During Stage 4, the Dispatcher Console reads the Favorite Territories field (FSL__FavoriteTerritories__c) from the user's Field Service user settings record (FSL__UserSetting__c). This field stores a JSON-formatted string mapping Service Territory record IDs to boolean values — for example: {"0HhXXXXXXXXXXXXX": true}. This JSON tells the console which territories to load as favorites.
When the field contains a malformed value — corrupted JSON, unexpected characters, truncated content, or an incorrectly structured string — the console's JavaScript parser fails silently. The loading process hangs indefinitely without raising a user-visible error.
Because the failure occurs at the data-parsing layer (not the access-control layer), no combination of permission sets, sharing rules, or profile changes resolves the issue.

Steps to Resolve the Dispatcher Console Hang at "Loading Service Territory Members" in Salesforce Field Service

  1. Identify the affected user's FSL__UserSetting__c record. Using Developer Console, Workbench, or a connected API tool, run a SOQL query on the Field Service user settings object (FSL__UserSetting__c). Filter by the FSL__User__c field equal to the 18-character Salesforce User ID of the affected dispatcher, and return the record Id, the Favorite Territories field (FSL__FavoriteTerritories__c), and the FSL__User__c field.
  2. Examine the value in the Favorite Territories field (FSL__FavoriteTerritories__c). A valid value is a JSON object with Service Territory record IDs as keys and boolean true as values. If the value is empty JSON ({}), contains non-JSON characters, is truncated, or has unexpected formatting, it is corrupt.
  3. Clear the Favorite Territories field (FSL__FavoriteTerritories__c) by setting it to null.
  4. Ask the affected user to reload the Dispatcher Console. All four loading stages should now complete successfully.
  5. After the console loads, the user can re-select favorite territories through the Dispatcher Console territory picker. This repopulates the Favorite Territories field (FSL__FavoriteTerritories__c) with a correctly formatted JSON value.
  6. If multiple users are affected, repeat Steps 1–5 for each user. Alternatively, run a bulk query on FSL__UserSetting__c to identify all records with a non-null Favorite Territories field value and inspect each for malformed content.
Nummer des Knowledge-Artikels

005388477

 
Laden
Salesforce Help | Article