You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/dynamics-365/field-service/rso/locked-booking-infeasible.md
+10-8Lines changed: 10 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,36 +4,38 @@ description: Resolves issues with booking locks in the Resource Scheduling Optim
4
4
ms.author: AnilMur
5
5
author: anilmur
6
6
ms.reviewer: mhart
7
-
ms.date: 02/07/2025
7
+
ms.date: 02/08/2025
8
8
ms.custom: sap:Resource Scheduling Optimization
9
9
---
10
10
# Locked booking is infeasible in Resource Scheduling Optimization
11
11
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.
13
13
14
14
## Symptoms
15
15
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:
17
17
18
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
19
20
20
## Cause
21
21
22
22
The tracing data points in the error message help you identify what went wrong. The violation types include:
23
23
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:
25
25
26
26
- 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).
30
30
31
-
-The eligibility check fails with a [constraint](/dynamics365/field-service/rso-optimization-goal#understand-constraints):
31
+
-Eligibility check failures:
32
32
33
33
-**Meets Required Skills**. A locked booking has an invalid match of the [resource skill characteristics](/dynamics365/field-service/set-up-characteristics).
34
34
-**Meets Required Roles**. A locked booking has an invalid [resource role match](/training/modules/configure-bookable-resources-urs-dynamics-field-service/).
35
35
-**Meets Resource Preferences**. A locked booking has an invalid ['must choose from' or 'restricted' resource](/dynamics365/field-service/resource-preferences).
36
36
37
+
For more information, see [Resource Scheduling Optimization constraints](/dynamics365/field-service/rso-optimization-goal#understand-constraints).
38
+
37
39
## Resolution
38
40
39
41
To solve the issue, update the booking settings and then rerun the Resource Scheduling Optimization:
0 commit comments