Skip to main content

Orchestrate schedules Task later than expected causing resource overload

Written by Charnjit Singh Dharival

  1. Unplan all Tasks that are currently planned on Resource Res1

  2. In the Task Planner, change the filter to: has sequence unplanned

  3. Click the Sequence column to sort the unplanned Tasks by Sequence ascending

  4. Set the Add to plan date (at the top of the Left Panel) to be: Mon 29 Jun 2026 07:35

  5. Select all the Tasks that are visible in that filter

  6. Click Replan

  7. Observe that Orchestrate plans the Task with Sequence 75 (Order 8703.01 OpStep 20) to start on Fri 3 July and it is overloaded with other Tasks on the Resource (with later Sequence numbers)

Expected behaviour

No valid reason why the Task for Order 8703.01 OpStep 20, which is planned first, shouldn’t be planned as the first Task on the Resource. (We checked ESD, it has no Usage KPIs, or Secondary Resources. And there are no other Op Steps for the Order on the Plan.) Even if there were a valid reason why it should be planned later, you wouldn't expect it to plan overloaded with other Tasks. (Checked that the Resource does not allow Task overlaps and is not Unconstrained.)


The functionality has been enhanced in Orchestrate version 7.83 or above. Please upgrade to this version.


Did this answer your question?