In Salesforce Field Service (SFS), when a user manually updates the Scheduled Start, Scheduled End, and Duration fields on a multi-day Service Appointment and saves the record, the Scheduled End may not retain the manually entered value. Instead, it automatically recalculates to a different time based on the service resource's operating hours and recorded absences.
This behavior is by design. Understanding how Salesforce Field Service calculates the Scheduled End helps avoid confusion when values change unexpectedly after saving.
How Scheduled End Is Calculated
In Salesforce Field Service, Scheduled End is calculated by adding the Duration to the Scheduled Start, factoring in the service resource's operating hours and recorded absences
Scheduled End − Scheduled Start = Estimated Duration
The Scheduled End field represents the time at which the Service Appointment is scheduled to end. If you are using the Field Service Lightning (FSL) managed package with the scheduling optimizer, this field is populated once the appointment is assigned to a resource.
Operating hours defined for Service Resources are used when calculating the Scheduled End date.
https://help.salesforce.com/articleView?id=pfs_optimization_theory_work_rules_match_time.htm&type=0
Real-Life Example: Engineer Calendar Scenario
Engineer Calendar -> 5:00 - 13:00
New changes->
Scheduled start:30/03/2023 9:30
Scheduled End:30/03/2023 15:30
Duration: 6 hours
After saving, the Scheduled End auto-updates to: 31/03/2023 07:30
Why? The resource's working hours end at 13:00. The appointment starts at 09:30, so the resource can only work 3.5 hours on 30/03 (up to 13:00). The remaining 2.5 hours carry over to the next working day, which starts at 05:00. Adding 2.5 hours to 05:00 gives a Scheduled End of 07:30 on 31/03/2023.
Note: If you update only the Scheduled End field directly (without changing Scheduled Start or Duration), the auto-recalculation does not trigger — the manually entered value is retained.
000395108

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.