When finite capacity is enabled, job scheduling enters WrkCtrScheduler.run() → scheduleEngine.run(). If no valid finite‑capacity time slot can be found, the scheduling engine repeatedly retries while iterating through resource calendars and resource group capacity.

In scenarios where capacity is fully consumed, this retry loop continues even though no feasible slot exists, leading to long scheduling times.

Proposed improvement

Introduce an early‑exit or optimization mechanism for finite‑capacity resolution, such as:

• Detecting “no feasible capacity” scenarios and failing fast
• Limiting internal retries per job/operation
• Avoiding repeated evaluation of the same calendar/resource constraints

Benefit

Reduced scheduling time, clearer failure behavior, and improved performance when finite capacity is enabled.