Schedule Exceptions
Schedule exceptions surface on the actionable inbox when a scheduling decision creates a soft conflict. They target Production Manager by default (Admins also see them).
These are different from schedule blockers. Blockers prevent publish. Exceptions are warnings that still allow publish but require human review.
Kinds
Tank Over Capacity
The total scheduled output for a tank on a date exceeds the tank’s configured capacity (work_centers.capacity_qty).
How to resolve: move one or more entries to another day or tank, or reduce planned output. The safety-net predicate auto-resolves once total scheduled output for that (tank, date) is at or below capacity.
Scheduled In The Past
A schedule entry has scheduled_date before today (UTC). This usually indicates stale draft edits or intentional back-dating.
How to resolve: move the entry to today or later, or resolve with a note if the back-date is intentional.
Not Covered By schedule_conflict
- Tank double-booking within a scenario is a hard API conflict (
POST /api/schedule/entries/upsertreturns HTTP 409). - Readiness blockers (missing work center, etc.) emit as
schedule_publish_blocker, notschedule_conflict.