Why Two Simultaneous Schedule Releases Can Conflict
Product: FeneVision CORE Module: Production / Scheduling Audience: Production Schedulers
Overview
When FeneVision releases a production schedule, it places temporary locks on the schedule, its orders, and the release date. These locks prevent data corruption that could occur if two users release schedules simultaneously and their changes conflict. Understanding these locks helps schedulers avoid errors and know what to do when a lock message appears.
How It Works
Two types of locks exist. A Release Date Lock is placed when either of the relevant release settings is unchecked — if another schedule attempts to release with the same release date, it is blocked until the first completes. A Schedule/Order Lock is placed when both release settings are checked — the specific schedule and its orders are locked, but other schedules can still release concurrently, provided they do not share orders with the locked schedule.
Key Rules / Things to Know
- Release Date Lock: Triggered when either release setting is unchecked. Blocks any other release sharing the same release date.
- Schedule/Order Lock: Triggered when both settings are checked. Only the specific schedule and its orders are locked — other schedules can release in parallel.
- If the same schedule is submitted for release more than once simultaneously, an error message appears indicating it is already being released.
- If an order is split across multiple schedules, those schedules cannot be released at the same time — attempting to do so triggers a lock error.
- Locks are temporary and release automatically when the original schedule release completes.
Tips
- Locks can be manually removed, this is useful when a lock is still in the system but not longer relevant, for example if it dates from a previous day.