Schedule Exceptions

Schedule exceptions surface in the Inbox when a scheduling decision creates a soft conflict. They are routed to the Production Manager role by default; Admins also see them.

These are different from schedule blockers. Blockers prevent a schedule from being published. Exceptions are warnings that still allow publish but require human review.

Kinds

Tank Over Capacity

The total scheduled output for a tank on a given date exceeds the tank’s configured capacity.

How to resolve. Move one or more entries to another day or tank, or reduce planned output. The exception auto-resolves once total scheduled output for that tank and date is at or below capacity.

Scheduled In The Past

A schedule entry has a scheduled date before today. 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.

What is not a schedule exception

• Tank double-booking within a scenario is a hard conflict — the system blocks the entry at edit time, before publish.
• Readiness blockers (missing tank or line, missing assignment, etc.) appear separately as publish blockers, not as exceptions.