|
| 1 | +--- |
| 2 | +title: Locked Booking Is Infeasible in Resource Scheduling Optimization |
| 3 | +description: Resolves issues with booking locks in the Resource Scheduling Optimization add-in for Microsoft Dynamics 365 Field Service. |
| 4 | +ms.author: AnilMur |
| 5 | +author: anilmur |
| 6 | +ms.reviewer: mhart |
| 7 | +ms.date: 02/18/2025 |
| 8 | +ms.custom: sap:Resource Scheduling Optimization |
| 9 | +--- |
| 10 | +# Locked booking is infeasible in Resource Scheduling Optimization |
| 11 | + |
| 12 | +This article helps you resolve the "Locked booking is infeasible" error that occurs in the [Resource Scheduling Optimization add-in](/dynamics365/field-service/rso-overview) for Microsoft Dynamics 365 Field Service. |
| 13 | + |
| 14 | +## Symptoms |
| 15 | + |
| 16 | +When a [locked booking](/dynamics365/field-service/booking-lock-options) can't respect all defined constraints, the Resource Scheduling Optimization request continues but skips the identified resources that have violations. You might encounter the following error message: |
| 17 | + |
| 18 | +> 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 |
| 19 | +
|
| 20 | +## Cause |
| 21 | + |
| 22 | +The tracing data points in the error message can help you identify what went wrong. The violation types include: |
| 23 | + |
| 24 | +- Time window violations: |
| 25 | + |
| 26 | + - The locked booking is outside of the resource's working hours. |
| 27 | + - The promised time window is invalid. |
| 28 | + - The travel time is invalid. |
| 29 | + - The locked booking conflicts with a [scheduled break time](/dynamics365/field-service/set-up-bookable-resources#add-work-hours). |
| 30 | + |
| 31 | +- Eligibility check failures: |
| 32 | + |
| 33 | + - **Meets Required Skills**. A locked booking has an invalid match to the [resource skill characteristics](/dynamics365/field-service/set-up-characteristics). |
| 34 | + - **Meets Required Roles**. A locked booking has an invalid match to the [resource role](/training/modules/configure-bookable-resources-urs-dynamics-field-service/). |
| 35 | + - **Meets Resource Preferences**. A locked booking has an invalid ["must choose from" or "restricted" resource](/dynamics365/field-service/resource-preferences). |
| 36 | + |
| 37 | + For more information, see [Resource Scheduling Optimization constraints](/dynamics365/field-service/rso-optimization-goal#understand-constraints). |
| 38 | + |
| 39 | +## Resolution |
| 40 | + |
| 41 | +To solve the issue, update the booking settings, and then rerun Resource Scheduling Optimization: |
| 42 | + |
| 43 | +1. Adjust the settings to resolve the identified violation. For example, update the [booking lock options](/dynamics365/field-service/booking-lock-options#booking-lock-options) or adjust the [Resource Scheduling Optimization constraints](/dynamics365/field-service/rso-optimization-goal#understand-constraints). |
| 44 | +1. Save the changes and [run the Resource Scheduling Optimization process](/dynamics365/field-service/rso-run-optimization) again. |
0 commit comments