You are here:
Shift Scheduling Considerations and Limits
Review considerations and limits for the shift scheduling tools.
Required Editions
| View supported editions. |
Shift scheduling tools are available with a Shift Scheduling or Workforce Engagement license. Depending on which license you have, keep these considerations and differences in mind.
- For Shift Scheduling, assign the Shift Scheduling Planner and Shift Scheduling Agent permission set licenses.
- For Workforce Engagement, assign the Workforce Engagement Analyst, Workforce Engagement Planner, and Workforce Engagement Agent permission set licenses.
- To map job profiles to Omni-Channel queues, Workforce Engagement planners use the Workforce Engagement Configuration app in Setup.
- The Match Queue scheduling rule is available only in Workforce Engagement with an Omni-Channel queue-based routing workflow. If you’re using Shift Scheduling or you’re using a workflow other than Omni-Channel queue-based routing, create a Match Skills scheduling rule to find the right types of support reps for your shifts.
- In Workforce Engagement, you can create a capacity plan based on historical workloads. You can then use shift templates and create shifts in bulk from a capacity plan. Shift Scheduling doesn’t include capacity planning.
- A planner can define shift segment types in Shift Scheduling and Workforce Engagement. In Shift Scheduling, the adherence threshold and background color fields don’t apply.
- How support reps view shift assignments and shift segments depends on whether you’re using
Shift Scheduling or Workforce Engagement.
- In Shift Scheduling, a support rep sees assigned shifts when they open the Shifts related list on their Service Resource record. Support reps can view shift segments in a related list on the shift. Access requires the Shift Scheduling Agent permission set.
- In Workforce Engagement, support reps can view shifts with defined shift segments in Agent Home. Only published shifts are visible. Admins must set up Agent Home and assign support reps the Workforce Engagement Agent permission set. In Workforce Engagement, shift segments also pair with Intraday Management to monitor under- or overstaffing, make real-time adherence updates, and send email notifications to support reps when their schedule changes.
- To update shift segments, planners can open a Shift record and modify segments. To update shift segments in Workforce Engagement, they can also use the Intraday Management dashboard.
General Limits
| Limit | Details |
|---|---|
| Maximum number of service resources per user | 1 per service resource type |
| Maximum number of service resource preferences | 1 per service resource |
Maximum number of records for these objects: Shifts, shift templates, shift scheduling operations, service resources, service territories, job profiles, operating hours, resource absences, time sheets, or scheduling constraints |
Platform behavior; 2000 records can be viewed without searching |
| Maximum number of time slots, service territory members, or time sheet entries | Platform behavior |
Scheduling Limits
| Limit | Details |
|---|---|
| Maximum number of shift segment types | 200 records |
| Maximum number of shift segments | 10 shift segment types per shift |
| Maximum number of shifts that can be batch assigned (using Assign) | 200 shifts at once |
| Maximum number of shifts on which Mass Shift Update can assign and update status | The number of shifts within a 90-day timespan. We recommend that you select less than 50,000 shifts. It can take a few hours to assign and update the status on 50,000 shifts. |
| Maximum number of scheduling rules | 50 |
| Maximum number of scheduling constraints | 50 |
Maximum number of records per page in these Shift Manager views
|
Up to 2000 records per page |
| Maximum number of Resource Absence records per page in the Shift Manager | Up to 300 records per page |
| Maximum historical data in adherence metrics (Workforce Engagement only) | Up to the past 365 days |
Did this article solve your issue?
Let us know so we can improve!

