Continuous loading when creating Datasets in Maps Territory Planning

This article explains what causes continuous loading or a timeout error when creating data sets or alignments in Salesforce Maps Territory Planning, and how to resolve it.

Why this happens

Depending on your Salesforce org setup, current activity, and the amount of data being loaded, Territory Planning can hit Salesforce platform limits when creating data sets or alignments, especially when using the default data processing batch size.

Steps to resolve

1. Reduce the number of fields in the report used to build the data set or alignment. If the issue continues, move to the next step.
2. Clean up any deleted data sets and alignments, since the size of the Territory Planning Unit object can affect performance.
   • In Salesforce, go to Installed Packages > Salesforce Maps > Configure > Territory Planning > Data, and click Permanently Delete.
   • Once you click Permanently Delete, an Apex batch job runs in the background to clean up the data. To check its status, go to Salesforce Setup and search for Apex Jobs, then look for the job named TPCleanupBatch.
3. If you still see the same error messages after trying steps 1 and 2, open a case with Salesforce Maps Support so the team can reduce the batch size and interval settings used for processing. Smaller, more frequent batches take longer to run but are less likely to hit a Salesforce limit.

Error messages you might see

This issue can show up with error messages like the ones below:

• "Unable to connect to the server (transaction aborted: timeout)."`

`BAD response from salesforce code 500 action :: GetUnitData message :: [{"errorCode":"APEX_ERROR","message":"System.LimitException: BlobValue length exceeds maximum: 6000000 (maps)"}]`