Skip to content

Commit 0d72c8c

Browse files
authored
updates based on comments
1 parent 4f84d98 commit 0d72c8c

File tree

1 file changed

+10
-8
lines changed

1 file changed

+10
-8
lines changed

support/dynamics-365/field-service/rso/locked-booking-infeasible.md

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -4,36 +4,38 @@ description: Resolves issues with booking locks in the Resource Scheduling Optim
44
ms.author: AnilMur
55
author: anilmur
66
ms.reviewer: mhart
7-
ms.date: 02/07/2025
7+
ms.date: 02/08/2025
88
ms.custom: sap:Resource Scheduling Optimization
99
---
1010
# Locked booking is infeasible in Resource Scheduling Optimization
1111

12-
This article presents possible causes and a resolution for 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.
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.
1313

1414
## Symptoms
1515

16-
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 message occurs:
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:
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

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

24-
- A locked booking can't fulfill the _Lock Booking Time Window_ or _Resource Break Time Window_ filter. The scenarios inlcude:
24+
- Time window violations:
2525

2626
- The locked booking is outside of resource working hours.
27-
- Invalid promised time window.
28-
- Invalid travel time.
29-
- Conflicts with a [scheduled break time](/dynamics365/field-service/set-up-bookable-resources#add-work-hours).
27+
- Promised time window is invalid.
28+
- Travel time is invalid.
29+
- The locked booking conflicts with a [scheduled break time](/dynamics365/field-service/set-up-bookable-resources#add-work-hours).
3030

31-
- The eligibility check fails with a [constraint](/dynamics365/field-service/rso-optimization-goal#understand-constraints):
31+
- Eligibility check failures:
3232

3333
- **Meets Required Skills**. A locked booking has an invalid match of the [resource skill characteristics](/dynamics365/field-service/set-up-characteristics).
3434
- **Meets Required Roles**. A locked booking has an invalid [resource role match](/training/modules/configure-bookable-resources-urs-dynamics-field-service/).
3535
- **Meets Resource Preferences**. A locked booking has an invalid ['must choose from' or 'restricted' resource](/dynamics365/field-service/resource-preferences).
3636

37+
For more information, see [Resource Scheduling Optimization constraints](/dynamics365/field-service/rso-optimization-goal#understand-constraints).
38+
3739
## Resolution
3840

3941
To solve the issue, update the booking settings and then rerun the Resource Scheduling Optimization:

0 commit comments

Comments
 (0)