Add new RSO topic

Author: Wendy Smith

…/rso/troubleshoot-booking-lock-issues.md …service/rso/locked-booking-infeasible.mdsupport/dynamics-365/field-service/rso/troubleshoot-booking-lock-issues.md renamed to support/dynamics-365/field-service/rso/locked-booking-infeasible.md support/dynamics-365/field-service/rso/troubleshoot-booking-lock-issues.md renamed to support/dynamics-365/field-service/rso/locked-booking-infeasible.md

@@ -1,41 +1,43 @@
 ---
-title: Troubleshoot booking locks from Resource Scheduling Optimization
-description: Resolves issues with bookings in the Resource Scheduling Optimization add-in for Microsoft Dynamics 365 Field Service.
+title: Locked booking is infeasible in Resource Scheduling Optimization
+description: Resolves issues with booking locks in the Resource Scheduling Optimization add-in for Microsoft Dynamics 365 Field Service.
 ms.author: AnilMur
 author: anilmur
 ms.reviewer: mhart
-ms.date: 12/19/2024
+ms.date: 02/04/2025
 ms.custom: sap:Resource Scheduling Optimization
 ---
-# Troubleshoot issues with booking locks in Resource Scheduling Optimization
+# Locked booking is infeasible in Resource Scheduling Optimization
 
 This article helps troubleshoot issues with booking locks in the [Resource Scheduling Optimization add-in](/dynamics365/field-service/rso-overview) for Microsoft Dynamics 365 Field Service.
 
 ## Symptoms
 
-A locked booking can't respect all defined constraints. The optimization request continues, but skips over the identified resources that have violations and displays the following error:
+If a locked booking can't respect all defined constraints, the optimization request continues, but skips over the identified resources that have violations. The following error occurs:
 
 **System failed to optimize some records. Inner error(s): Locked booking is infeasible, reason: `Violation`. Tracing data points: `RequirementId`, `RequirementName`, `BookingId`, `BookingName`, `ScheduledTimeWindow`, `FullTimeWindow`, `ArrivalTime`, `Lock Type`**
 
-## Resolution
-
-The tracing data points help you identify what went wrong. Try updating the booking settings to address the violation reason before running Resource Scheduling Optimization again.
+## Cause
 
-### Violation types
+The tracing data points in the message help you identify what went wrong. The violation types include:
 
-- The locked booking cannot fulfill the time window filter.
+- The locked booking can't fulfill the time window filter.
 
   - **LockBookingTimeWindowFilter**. Potential scenarios:
     - Locked booking is outside of resource working hours
     - Invalid promised time window
     - Invalid travel time
 
-  - **ResourceBreakTimeWindowFilter**. A locked booking conflicts with a [scheduled break time](set-work-hours-resource.md).
+  - **ResourceBreakTimeWindowFilter**. A locked booking conflicts with a [scheduled break time](dynamics365/field-service/set-work-hours-resource).
 
 - The eligibility check failed with constraint.
 
-  - **MeetsRequiredSkills**. A locked booking has an invalid match of the [resource skill characteristics](set-up-characteristics.md).
+  - **MeetsRequiredSkills**. A locked booking has an invalid match of the [resource skill characteristics](dynamics365/field-service/set-up-characteristics).
 
   - **MeetsRequiredRoles**. A locked booking has an invalid [resource role match](/training/modules/configure-bookable-resources-urs-dynamics-field-service/).
 
-  - **MeetsResourcePreferences**. A locked booking has an invalid [“must choose from” or “restricted” resource](resource-preferences.md).
+  - **MeetsResourcePreferences**. A locked booking has an invalid [“must choose from” or “restricted” resource](dynamics365/field-service/resource-preferences).
+
+## Resolution
+
+Update the booking settings to address the violation reason and then run Resource Scheduling Optimization again.

support/dynamics-365/field-service/toc.yml

@@ -63,6 +63,8 @@
 
 - name: Resource Scheduling Optimization add-in
   items: 
+    - name: Locked booking is infeasible
+      href: rso/locked-booking-infeasible.md
     - name: Optimization request fails to modify some bookings
       href: rso/system-failed-modify-bookings-error.md
     - name: '"Object reference not set to an instance of an object" error'