If the dispatcher tries to create non-work order events that overlap with a pre-existing blocked event or external event in the technician calendar, RTO recognizes this action as a conflict as the technician cannot handle two tasks at once. Best practice is to avoid any kind of overlap within the RTO horizon.

If the business scenario requires the creation of overlapping events, RTO respects such events and marks the route unoptimizable.

Alternatively, RTO honors the non-work order events created by the dispatcher on open slots outside the dispatch threshold time window. RTO does not schedule any work orders in those timeslots.