Skip to content

Commit 9ea4677

Browse files
authored
Edit review
1 parent 4b963fb commit 9ea4677

File tree

1 file changed

+12
-12
lines changed

1 file changed

+12
-12
lines changed
Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
title: Locked Booking is Infeasible in Resource Scheduling Optimization
2+
title: Locked Booking Is Infeasible in Resource Scheduling Optimization
33
description: Resolves issues with booking locks in the Resource Scheduling Optimization add-in for Microsoft Dynamics 365 Field Service.
44
ms.author: AnilMur
55
author: anilmur
66
ms.reviewer: mhart
7-
ms.date: 02/11/2025
7+
ms.date: 02/18/2025
88
ms.custom: sap:Resource Scheduling Optimization
99
---
1010
# Locked booking is infeasible in Resource Scheduling Optimization
@@ -13,32 +13,32 @@ This article helps you resolve the "Locked booking is infeasible" error that occ
1313

1414
## Symptoms
1515

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 over the identified resources that have violations. You may encounter the following error message:
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:
1717

1818
> 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
1919
2020
## Cause
2121

22-
The tracing data points in the error message help you identify what went wrong. The violation types include:
22+
The tracing data points in the error message can help you identify what went wrong. The violation types include:
2323

2424
- Time window violations:
2525

26-
- The locked booking is outside of resource working hours.
27-
- Promised time window is invalid.
28-
- Travel time is invalid.
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.
2929
- The locked booking conflicts with a [scheduled break time](/dynamics365/field-service/set-up-bookable-resources#add-work-hours).
3030

3131
- Eligibility check failures:
3232

33-
- **Meets Required Skills**. A locked booking has an invalid match of the [resource skill characteristics](/dynamics365/field-service/set-up-characteristics).
34-
- **Meets Required Roles**. A locked booking has an invalid [resource role match](/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).
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).
3636

3737
For more information, see [Resource Scheduling Optimization constraints](/dynamics365/field-service/rso-optimization-goal#understand-constraints).
3838

3939
## Resolution
4040

41-
To solve the issue, update the booking settings and then rerun the Resource Scheduling Optimization:
41+
To solve the issue, update the booking settings, and then rerun Resource Scheduling Optimization:
4242

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).
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).
4444
1. Save the changes and [run the Resource Scheduling Optimization process](/dynamics365/field-service/rso-run-optimization) again.

0 commit comments

Comments
 (0)