Skip to main content

Scheduling Conflicts

A conflict occurs when two schedule blocks overlap on the same line. RunMark warns you about conflicts but allows you to save them — you remain in control.

Why conflicts happen​

  • A run takes longer than expected and bleeds into the next block
  • A block was moved without checking what's already there
  • Two runs were scheduled back-to-back with no changeover buffer

Resolving a conflict​

Move one block to a different time. Click the conflicting block on the Gantt, open the detail panel, and reschedule it to a non-overlapping time slot.

Move one block to a different capable line. If another line can run the same SKU, reschedule the conflicting block there. Check the line's capability list in Lines settings.

Delete and recreate. If a block belongs to an order you can reschedule freely, delete the block from the Gantt and use the Orders page to re-schedule it.

Preventing conflicts​

  • Leave a changeover buffer between back-to-back jobs on the same line by setting accurate changeover times in the line configuration.
  • After scheduling a block, check the Gantt view before adding the next block on the same line.
  • Ask the Production Assistant: "What's scheduled on Line 1 this week?" to see what's in the queue before scheduling.