---
schema_version: "1"
id: 2a909b22acc0cf4b82f17a0a1048f54ff517f77b0f2d1efa4c3bea2d980a22d9
title: Considerations for Performance Improvement in Salesforce Scheduler
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/ls_considerations_for_performance_improvements.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.ls_considerations_for_performance_improvements.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: da6b903577b89520e448d852e216289c7fae58ed619649dcbc501ed3c21c4ad2
description: Scheduling is a performance-intensive process. To get the best out of Salesforce Scheduler, here are some things to keep in mind when you set up Salesforce Scheduler.
products:
  - Scheduler
  - Salesforce Platform
release: "264"
---
# Considerations for Performance Improvement in Salesforce Scheduler

Scheduling is a performance-intensive process. To get the best out of Salesforce Scheduler, here are some things to keep in mind when you set up Salesforce Scheduler.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience.</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong> and <strong>Unlimited</strong> Editions</td></tr></tbody></table>

- As the number of qualified service resources increases, Salesforce Scheduler takes longer to fetch the list of service resources available for a time slot.
    
    For a duration of 14 days, we recommended that you keep the number of qualified resources to 20. If you enable skill matching and engagement channel types, then limit the service resources that are associated with the same work type group and the same engagement channel type to 20 per service territory. The limitation applies if you use Salesforce Scheduler standard flows.
    
    ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-scheduler-264-0-0-production-enus/0530be2f-891f-4263-a0d7-96ddca56a717/images/icon_note.png)
    
    Note If more than 20 service resources are available for a time slot, then use Appointment Distribution to limit the list of qualified service resources.
- To load the time slots faster, reduce the number of days cached for available time slots.
    - If you use standard flows, the value of the Time Slot Preload Multiplier attribute on the Select Service Appointment Time Slot screen component determines the number of days that time slots are fetched for by each server call. For example, if your device's page can show time slots for 7 days and the value of the attribute is 2, then Salesforce Scheduler fetches time slots for 14 days (7x2). To reduce the load, fetch time slots for only 7 days by setting the value of the attribute to 1.
    - If you use APIs, specify a shorter duration using the Start Time and End Time fields in the API request. The default duration is 31 days.
- If you don’t consider Salesforce calendar events to determine the availability of service resources for appointments, deselect the Check Salesforce Calendar for Resource Availability option in the scheduling policy.

#### See Also

- [Flow Screen Component: Select Service Appointment Time](https://help.salesforce.com/s/articleView?id=platform.ls_flowscreencmp_select_srvc_appt_time.htm&release=264.0.0&type=5 "Enables users to select a service appointment time.")
- [Available Territory Slots](https://developer.salesforce.com/docs/atlas.en-us.chatterapi.meta/chatterapi/connect_resources_available_territory_slots.htm)