Skip to main content

Error: 'Please check the dependencies on the following tasks' when locking lots of tasks or planning works orders

Written by Charnjit Singh Dharival

Lock a bunch of tasks and the following message generates:-

An unexpected error occurred. Please report this problem to your system administrator with the following information:
Orchestrate5.PlanningException: Please check the dependencies on the following tasks:

Process , Order 12345 , op step 100
and
process , Order 12345 , op step 200

When planning works orders the following message generates:

Order Code: 123456.00

Please check the following dependencies on the following tasks:

Process name , Order 12345 , op step 100

process name , Order 12345 , op step 200


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

If you are not in a position to upgrade yet, there is a workaround to get around this by applying a 0.001 to max offset on the Start-to-Start Min 0 Max 0 dependency between the Tasks, so that min and max are not both exactly zero. Please complete the following steps:

  1. Log into Orchestrate and open the plan

  2. Select Orders, Works Orders

  3. Type the relevant order number and click Search

  4. Click Find On Plan

  5. Select Op Step column heading to order by op step

  6. Select the relevant op step and resource row

  7. Tick Locate Task On Plan

  8. Right-click the relevant task and select Edit Task Dependencies

  9. Select the successor tab and enter 0.001 in the Target Min Offset (Hours)

  10. Click Add

When this message occurs due to planning works orders, check the maximum offset e.g. 12 hours. Looking at the process steps, op step 10 had duration of 9 hours and op step 20 had a work duration of 6 hours (total 15 hours). You can't have the total work duration of linked op depdencies longer than the offset time. Change the maximum offset to 24 hours (like the other existing op steps), and then the works order planned successfully

Did this answer your question?