Find and resolve conflicts

Outcome

In this guide you do four things:

Create a deliberate scheduling overlap.
See it in all three places where conflicts appear.
Resolve it on the board.
Return the list to “No conflicts detected. All scheduled requests meet their requirements.”

Before you begin

A workspace with at least one space and two schedulable requests. Create your first schedule gets you there.
The Editor or Admin role.
Background reading: Understanding conflicts.

Step 1 — Manufacture a collision

On Utilization → Stations, schedule request A onto a station for tomorrow.
Schedule request B onto the same station at the same time.

Orkyo warns you during placement, because overbooking is one of the validations. Continue anyway. Real schedules collect conflicts through later edits all the time, and that is exactly why detection exists.

Step 2 — See where it surfaces

The same conflict now shows in three places:

On the board — a conflict indicator marks the affected placements.
On the request — open A or B. A banner counts the conflicts on it and gives the message of each one.
In Insights → Conflicts — a card labeled Scheduling Overlap. It shows the schedule and a “View other request” link to the counterpart. The summary line now reads “1 conflict found in scheduled requests.”

Step 3 — Resolve it

On Utilization → Stations, drag request B to a free slot. Use a different time, or a different suitable station. The conflict indicator disappears as detection runs again.

There are two alternatives. Which one applies depends on what the conflict tells you.

The other request is the one to move. Use the “View other request” link on the card to decide which placement is wrong.
The capacity is wrong. If the station genuinely holds both, raise its Capacity (Stations). Do not move the work. The conflict kind is then Capacity Exceeded, and the fix is the data, not the schedule.

Step 4 — Confirm zero

Go back to Insights → Conflicts. The list is empty: “No conflicts detected. All scheduled requests meet their requirements.”

Step 5 — Make it a habit

Scan Insights → Conflicts at a fixed rhythm, at the start of a shift or the start of a week. The filters on Insights also chart the Conflict trend, which tells you whether the schedule gets healthier.
Treat a recurring conflict kind as feedback on your model. Chronic Capacity Exceeded is a capacity problem. Chronic Capability Mismatch after edits means that somebody changes capabilities without a check of the dependent schedules. Chronic Dependency Violation means the sequence you recorded is not the sequence the shop floor works to — correct one or the other.
You can export the conflicts as CSV from the Conflicts page, for review meetings. See Import and export.
Select Ask the assistant on a conflict to get an explanation and a proposed correction. See AI assistant.