Merge pull request #7906 from MicrosoftDocs/fs-rso-troubleshooting-freshness

AB#3176: FS - RSO Freshness updates

Author: lucciz01

support/dynamics-365/field-service/rso/requirement-not-scheduled-in-rso.md

@@ -4,7 +4,7 @@ description: Provides a resolution to solve the issues with unscheduled requirem
 ms.author: AnilMur
 author: anilmur
 ms.reviewer: mhart
-ms.date: 10/18/2024
+ms.date: 12/19/2024
 ms.custom: sap:Resource Scheduling Optimization
 ---
 # Requirements not scheduled in Resource Scheduling Optimization

support/dynamics-365/field-service/rso/system-failed-modify-bookings-error.md

@@ -4,7 +4,7 @@ description: Resolves issues with optimization requests in the Resource Scheduli
 ms.author: AnilMur
 author: anilmur
 ms.reviewer: mhart
-ms.date: 10/19/2023
+ms.date: 12/19/2024
 ms.custom: sap:Resource Scheduling Optimization
 ---
 # An optimization request fails to modify some bookings
@@ -15,14 +15,18 @@ This article helps administrators troubleshoot optimization requests in the [Res
 
 An [optimization request](/dynamics365/field-service/rso-schedule-optimization#monitoring-optimization-requests) fails with the "System failed to modify some bookings" error message.
 
-## Resolution
+## Cause
 
 The optimization request can fail in the following scenarios:
 
 - A user manually updates a booking during a Resource Scheduling Optimization run. Resource Scheduling Optimization won't overwrite the changes.
-- A workflow or plug-in updates the same bookings during a Resource Scheduling Optimization run. Resource Scheduling Optimization won't overwrite the changes your other system logic did.
-- Multiple Resource Scheduling Optimization schedules share the same resources and run at the same time. For analysis and troubleshooting, check the following options:
+- A workflow or plug-in updates the same bookings during a Resource Scheduling Optimization run. Resource Scheduling Optimization won't overwrite the changes made by other system logic.
+- Multiple Resource Scheduling Optimization schedules share the same resources and run at the same time. If schedules include overlapping resources, requirements, and bookings, a later schedule is cancelled with a status of blocked.
+
+## Resolution
+
+For analysis and troubleshooting, check the following options:
 
-  - Review the optimization request booking grid and inspect the operation details column for each requirement and booking.
-  - Check if multiple schedules that share the same resources, requirements, and bookings run at the same time. If that's the case, update the schedules to run sequentially or reconfigure them to avoid overlaps.
-  - Check if any other user or workflow tries to update a booking during the optimization request run.
+- Review the optimization request booking grid and inspect the **Operation Details** column for each requirement and booking.
+- Check if multiple schedules that share the same resources, requirements, and bookings run at the same time. If that's the case, [update the schedules to run sequentially](/dynamics365/field-service/rso-requirement-dependency) or reconfigure them to avoid overlaps. For more information, see [Resolve booking conflicts in Resource Scheduling Optimization](/dynamics365/field-service/rso-handling-resolving-booking-conflicts).
+- Check if any other user or workflow tries to update a booking during the optimization request run.

support/dynamics-365/field-service/rso/troubleshoot-bookings-in-rso.md

@@ -1,10 +1,10 @@
 ---
 title: Troubleshoot bookings from Resource Scheduling Optimization
-description: Resolves issues with bookings in the Resource Scheduling Optimization add-in for Dynamics 365 Field Service.
+description: Resolves issues with bookings in the Resource Scheduling Optimization add-in for Microsoft Dynamics 365 Field Service.
 ms.author: AnilMur
 author: anilmur
 ms.reviewer: mhart
-ms.date: 10/19/2023
+ms.date: 12/19/2024
 ms.custom: sap:Resource Scheduling Optimization
 ---
 # Troubleshoot issues with bookings in Resource Scheduling Optimization
@@ -37,17 +37,21 @@ Booking status has a **Scheduling Method** field that dictates how Resource Sche
 
 ### Block Resource Scheduling Optimization from moving past bookings
 
+The [optimization range](/dynamics365/field-service/rso-optimization-scope#create-an-optimization-scop) is the time range during which bookings can be created, updated, or deleted. It defines the "output" side, but not the "input" side. The optimization range doesn't determine what bookings are included.
+
+To block changes to past bookings, consider the following options:
+
 - Set the booking status to **Don't Move**.
-- Remove the booking from the booking view.
+- Remove the booking from the booking view. To ensure that optimization runs, consider only future bookings that occur after a specific point. In the **Booking View** of optimization scope, you can select a value in the **On or After** field.
 - Lock the booking to a time or time range in the past.
-- Set a promised date from/to while enabling the time window constraint.
+- [Set a promised date from/to](/dynamics365/field-service/schedule-time-constraints#schedule-a-requirement-in-a-time-frame) while enabling the time window constraint.
 
 ### Bookings in simulation status
 
-If an exception or error happens when an optimization schedule is still running, you might see some overlap on the schedule board. Some bookings are created or updated from the latest run, while other bookings from the previous run failed to be deleted due to an issue. To avoid this issue, the optimization process uses transactional bookings in the *Simulation* status.
+If an exception or error occurs during an optimization schedule run, you might see some overlap on the [Schedule Board](/dynamics365/field-service/schedule-board-tab-settings#board-view-settings). Some bookings are created or updated from the latest run, while other bookings from the previous run failed to be deleted due to an issue. To avoid this issue, the optimization process uses transactional bookings in the *Simulation* status.
 
 During the optimization process, the create, update, and delete operations are visible. All new, updated, and to-be-deleted bookings are simulated. If the optimization run completes successfully, these simulated bookings become real bookings. During the optimization run, simulation status bookings are transparent and move around the schedule board. When the run completes, simulation bookings change to real bookings with a solid color.
 
 If an exception occurs and the optimization request fails, these simulation bookings remain in simulation status for troubleshooting purposes unless you manually delete them. Otherwise, a system job deletes them automatically every two weeks.
 
-You can hide simulation bookings by changing the schedule board settings. Select the gear icon on the top right, and then select the **Hide Canceled** option.
+You can hide simulation bookings by changing the [schedule board settings](/dynamics365/field-service/schedule-board-tab-settings#board-view-settings). Select the gear icon on the top right to open the **Scheduler settings**, and then disable the **Show canceled** option.