Field Service Platform and Managed Package patch notes.
March '26
- Managed Package (260.7)
- Fixed an issue with the Dispatcher Console where the Agentforce explanation used the wrong label and showed “high start time” instead of “late start time”.
- Fixed an issue where Change Status didn’t render correctly when you opened it from the list, Gantt, or popover.
- Fixed an issue where Fill Resource Gaps sent the wrong current time into scheduling optimization when the technician’s time zone was far from the dispatcher’s, which could throw off gap detection in extreme time zone scenarios.
- Fixed an issue where the resource sharing job ran on every service appointment status change even when sharing didn’t need to refresh, and added optional configuration.
- Fixed an issue where booking with schedule over lower priority and reshuffle on left lower-priority appointments overlapped on the Gantt instead of unscheduling them.
- Fixed an issue where a live update that removed an assigned resource could make the service appointment disappear from the Gantt and lists instead of leaving it unscheduled.
- Fixed an issue where processing could throw an error while reading scheduling optimization response data.
- Fixed an issue where optimization could list the same task more than once in scheduled results on mobile, which could make the schedule look wrong on the device.
February '26
- Managed Package (260.5 and 260.6)
- Fixed an issue where Dispatcher Console could still send network requests in the background after your session became inactive, even though a blocking refresh message was shown.
- Fixed an issue where dates and times were wrong during appointment booking for the Israel-Hebrew locale because that locale code wasn't mapped to a supported Hebrew value for the date library.
- Fixed an issue where scheduling optimization could return the wrong HTTP response when multiple optimization requests ran at the same time.
- Fixed an issue where unscheduling a dispatched service appointment failed with a validation error while calendar events and assigned resources were being cleaned up during calendar sync.
- Fixed an issue where the next and previous controls in Dispatcher Console long-term view did not move the visible schedule forward or backward by a full week.
- Fixed an issue where the resource availability service returned shifts that extended beyond the requested start and end dates in full instead of trimming them to the range specified.
- Fixed an issue where a long-running scheduling optimization could cause a later scheduling or rules operation to time out sooner than expected.
January '26
- Managed Package (260.3 and 260.4)
- Fixed an issue where drag and drop failed because the service territory member definition was missing.
- Fixed an issue where Unscheduled Service Appointments was populated even though it should have been 0.
- Fixed an issue where rule validation failed because there was no access to one of the service appointments in the complex work chain.
- Fixed an issue where Resource Schedule Optimization ignored the Required Resource Preference for service appointments that were outside the domain.
- Fixed an issue where incorrect travel times were calculated when an absence was fully contained within a scheduled service appointment.
- Fixed an issue where Relevance Groups didn’t work with the Extended Match work rule.
- Fixed an issue where the optimization request failed because a scheduled service appointment had a dependency with a canceled service appointment.
- Fixed an issue where the Gantt scrolled 24 hours instead of 3 hours when moving forward or backward in the In Day view.
- Fixed an issue where the Data Cloud connection failed during the TLS handshake.
- Fixed an issue where resource availability was silently dropped on certain days due to conflict.
- Fixed an issue where ids were added to the Travel To or Travel From field tooltips on the Gantt.
- Fixed an issue where the SchedStartTime filter excluded unscheduled service appointments with dependencies.
- Fixed an issue where the parsing of numbers in the rule violation text was incorrect.
November '25
- Platform (258.10 and 258.11)
- Fixed an issue where a work capacity limit of 0% was not being enforced.
- Fixed an issue where the CSI (Conversation Service Integration) invocable action required accountId as a mandatory input parameter, causing errors when Work Orders didn't have an associated Account.
- Managed Package (258.7 and 258.8)
- Optimized SOQL queries in the InDay composite API to reduce query count and stay within limits during concurrent operations.
- Fixed an issue where travel calculations incorrectly used shift intervals from the secondary Service Territory Membership when the primary territory had no availability.
- Fixed an issue where travel times were missing when service appointments were dragged and dropped onto holiday shifts in the flow.
October '25
- Platform (258.8 and 258.9)
- Fixed an issue where sorting on the name in the work order related list caused high CPU usage.
- Fixed the step "Let service resources access their dispatched service appointments and related work orders" in the Field Service Initial Setup in Salesforce Go.
- Fixed an issue where the SFS Studio Setup Enabled permission was incorrectly set to true by default in new Unlimited, Enterprise, and Professional Edition orgs. This permission will no longer be enabled automatically upon org creation.
- Fixed an issue where the Activity Timeline component was not supported on the Work Order object in Lightning communities. The Work Order object now displays the Activity Timeline, allowing users to see New Task and New Event actions as expected.
- Managed Package (258.5 and 258.6)
- Fixed an issue where scheduling failed because a service appointment slot was taken by another service appointment.
- Fixed an issue where a Null Pointer Exception occurred in the RSOPreProcessor class when running Resource Scheduling Optimization (RSO) jobs with a custom boolean field instead of explicit service appointment IDs.
- Fixed an issue where repeated calls to addTerritoryAttributesToResource caused performance degradation due to inefficient runtime complexity.
- Fixed an issue where a resource absence disappeared from the Gantt chart when the resource’s service territory had a large number of service territory members.