Conflict

A conflict in Omniscol is a situation where two constraints cannot be satisfied at the same time. Examples:

• a teacher assigned to two lessons on the same time slot,
• a room booked by two lessons at the same time,
• a group of students expected in two places at once,
• a lesson that does not respect the specialisation required for its subject,
• a lesson whose total capacity (sum of the assigned rooms) is lower than the group's headcount,
• an alignment whose aligned groups have different numbers of hours.

Real-time detection

Omniscol detects conflicts as you enter data, not only at generation time:

• a red banner at the top of the hours distribution screen,
• an icon on the affected lessons and classes,
• a clickable list of conflicts (the "magnifier" leads to the details).

Intentional conflicts

Not every conflict has to be resolved. Some are intentional:

• the same group on an exam + an extra-time room (the same cohort of students is expected in two rooms depending on conditions),
• headcount > room capacity when you know that not all enrolled students will attend.

You can leave the conflict; the alert stays displayed but does not block operation.

Blocking conflicts

Some inconsistencies prevent the automatic generation from succeeding:

• no room compatible with a subject + a number of hours,
• a teacher whose availability is entirely incompatible with their courses,
• a structurally impossible alignment.

These conflicts are flagged as critical; as long as they exist, the Generate timetable button remains unavailable.