What is not supported

Describes RotoScheduler 0.3.2 · checked 2026-10-10 Xiaoyongs-Mini

Workbook and settings

What is not supported	What you will see, and what to do
Editing shared facts in RotoScheduler, or writing them back from the plan	Mold names, dimensions, shapes, weights, copies, parts per cycle, materials and process classes, arm geometry and maximum load, and mold-to-mold clearance are maintained in RotoSpider. The displayed fields in `Factory inputs` are read-only. Save in RotoSpider, then use `Take from masterdata` and `Apply`.
Workbook changes reaching the plan automatically	The plan keeps its previous inputs until you take and apply them. Review the proposed inputs and the list of work taken off.
Taking after another edit in the same opening	The take button is no longer offered. Apply or cancel the edit, reopen `Factory inputs`, then take. The same applies after `Read orders`.
Two people editing the same workbook or plan at once	A save can be refused because the file changed or the plan is already in use. Use one editor at a time; finish and close that edit before the other person opens the file again.
Taking the workbook color over an existing mold's plan color	Existing molds keep their RotoScheduler colors, including automatic colors. Only a mold new to the plan starts with its workbook color. Change an existing color in `Factory inputs`; a color-only edit uses `Save colours`.
Reading good share or minimum stock from the workbook	The workbook has no good-share column, and its minimum stock is not read into the plan. Enter `Good share %` and `Basis` on the mold, and a stock rule on each product, in `Factory inputs`. Record stock on hand with `Count` in the inspector.
Taking every RotoSpider setting	Only the minimum and target mold-to-mold clearance are taken. Do not assume other layout settings changed the plan; use the planning rules supplied in its plan file.

Molds and arms the plan cannot take

What you will see	What to do
`Rows left out` lists a mold with missing or zero dimensions or weight, or a shape unavailable on this computer.	Complete the workbook row or restore the shape files, then take again. A product still naming an omitted mold prevents `Apply`.
`Apply` refuses a mold with no name or two molds with the same name.	Give every mold row a nonempty, unique name in the workbook, save and take again.
Renaming a mold in the workbook makes a new mold; a product still names the old one.	Select the correct `Mold ID` for that product before applying, or cancel and restore the workbook name.
`Apply` refuses removal of a mold still named by a machine's stated cycle time for that mold, or a recorded mold pairing.	Cancel the take. Keep the referenced mold until those factory facts have been corrected. Where the app has no field for the fact, ask support to correct the plan data. A line naming a copy of a dropped mold skips that copy.
Retiring a mold copy, matching copies across a renamed mold, or knowing which copy a lower workbook count removed	A lower count keeps the plan's copies. `Take from masterdata` lists the mold with both counts and the kept IDs. A renamed mold gets new copies and IDs. Put a copy out of use with `Record stop` beside `Count`.
An arm keeps its geometry after a take.	Match `Machine model` exactly to the workbook model and check that the workbook includes that arm type. Apply any model or type edit, reopen and take again. A new machine-day or arm may otherwise keep default dimensions.
A minimum-machine entry written as a model name or with an arm suffix does not restrict the machines available to a mold.	Do not rely on that text as a limit. Set each order's `Allowed machines` to the machines the factory permits.

Starting and changing a plan

Starting with no molds or machine-days is not supported. Such a document is refused and may offer only Retry, without access to Factory inputs. Start from the supplied sample; Blank manual plan clears the production plan while keeping its factory inputs.
Add machine-day and Add arm do not add a resource across every date. Check each required date and use Add date for further dates. Take from masterdata again after applying new arms or arm types.
A supplied sample is for trying the screens. Its orders and stock rules are examples, not your order book, counted stock or production commitments.
Undo does not cross an Apply of factory inputs, including a take, unless that Apply changed only the plan's dates. Save a file before changing them. Work taken off is not put back automatically. To reverse a shared fact, correct it in RotoSpider and take again.
A changed mold group that no longer fits comes off as a whole, including other molds on that arm in that cycle. Further groups can come off after it. Review the list above the board and place only the work that still fits. A change that breaks protected work, reported or dispatched, is refused instead.

Counts, deliveries, reports and the test

A mold that always makes several products in fixed proportions, and one product standing in for another, are not supported.
Where orders for one product allow different machines, pieces are given in the stated order to the earliest requirement they may serve. This does not promise the best giving across all those orders.
Stock on hand is counted at the plan's first date.
Lateness already incurred is not shown for a stock rule, nor in minutes. Pieces already delivered count as Delivered late (good pieces) only, never also as Produced late (good pieces).
A count's pieces beyond what the previous count and the reports since explain have no production date. Given to an order due before the count's day, they show as Production date unknown (good pieces).
A delivery read from totals is dated the day those totals run through. Pieces that left earlier count as Delivered late (good pieces) when that day is after the order's due date.
A load with several products moves as a whole; moving only some of its mold copies is not supported. Surplus removable only by using fewer copies is shown but calls for nothing.
An overnight cycle from before the plan's first date is not carried into that first day's timing. Copies seen before that date do open the first day.
Release dates, an offer to plan the rest again, and timing an already late day again are not included. The test offers no action and never accepts or dispatches a plan by itself.
A new report covering several cycles in one line is not supported. The daily entry writes one line per reported cycle; an older wider report is corrected whole.
Correct replaces a reported range whole. A correction of only part of it is not supported.
Changing a mold's copies in the daily entry is not supported when that mold makes more than one product in the load.
On a position protected by a dispatch, a report cannot name another load or other copies than that dispatch's.
A reported load that today's facts refuse (layout, co-loading, thermal or a group) cannot be accepted. Correct the facts or the stated load.
On an undispatched day, a stop uses the declared cycle grid, not the load's projected times. It does not re-time the grid after a stop ends.
A stop planned ahead cannot be entered. Keep planned shutdowns in the machine-days.
A machine or arm stop dated on a day with no machine-day of its machine covers nothing; date it on the first machine-day it stops.
A stopped arm keeps its mold copies. A stop does not release or move them. The effect on another arm through the copies an impossible load would mount is not supported.
A line about where a copy is during a machine-day affects planning from the next opening; that day’s planned work stays as it was. A line with no later opening changes only the place shown.
The order of copy moves between different machines' openings on one production date is not supported.
The production log does not supply a station or an opening shot.
A green place can still be refused at the drop when a copy the run needs cannot arrive from where it is in time; the drop's check names the copy.
A green place can still be refused at the drop when every copy of the mold is out of use; the drop's check names the stop.
Generate can propose a mold removal before the shift, but not after a production cycle.
The plan's minutes after a stop's end stay unchanged. Resuming an interrupted cycle is not supported.
The full stop form is not included; the inspector records a machine, arm or mold copy, its start, estimate, confirmed end and reason, and after cycle for an arm.
Stock receipts and issues other than Count, Report and Delivery, returns, and negative deliveries are not supported.
The orders view, a printed (PDF) sheet and the production-log archive are not included. The inspector contains Count, Delivery, Daily entry and Correct controls and the test's result.
A customer list and customers read from a plant's file or Read orders are not included. Type the customer in Factory inputs.
A reported cycle's order allocations are not compared in Changed since dispatch. Who changed what and why is not recorded.
Count does not recognize a working window that began the day before when choosing its default after midnight. Check Through day before applying it.
A reminder of days not logged is not included.
A product remains after its last order is removed. To remove a mold it still names, first give the product another mold; otherwise Apply is refused.
A hand assignment on a machine an order does not allow still loads the product there; that order receives none of those pieces and remains unmet.
An order whose Start by is after the plan's last date receives no planned pieces yet. Pieces dispatched or placed by hand for it count in the product's planned pieces but are not given to it until counted; only those beyond the product's maximum show as surplus. The order shows not placed.
After a hand edit or reopening, the app gives computed quantity and date reasons. It does not retain Generate's reasons for work it could not place.

For the entry steps and the meaning of the test, see Count, Delivery and Report. A date change and a change of a dispatched day's facts may need separate Apply acts, as described in Describe the factory.

What else fits in a load

A loaded cycle still has no light. Its + checks what else fits only when opened; an edit, a change of the selection or of the plan closes the list.
The + is offered on a loaded cycle even when nothing fits. The opened list then says Nothing else fits in this load.
Each pick adds one copy for one cycle. For more copies or cycles, use the job's Copies and Cycle slots fields and drop it onto the cycle.
The pieces go to the product's jobs as with a drop. The row's first job is selected, but is not promised the pieces first.
The list uses the visible jobs with pieces left to plan on this machine. A mold no such job needs is not offered. A closed day, an unavailable arm, a dispatched or reported position and a day box offer no +.
A green row's pick can still wait for Apply job assignment with warning where the engine's signal is yellow for a note the light does not colour, such as an unverified process window, as a green light's drop does today.
A refused mold is counted, not listed; its reason is in the count's hover.
The web demo has no +.

Stretch or shorten a run

The run's length changes in the inspector's Run cycles field; the board has no handle to drag.
A stretch that runs out of the day's cycles continues on the next days of the same arm; a run shortens on its own day only, from its end.
A stretch beyond what the mold's products may still make is refused (This load would exceed the maximum to make for product …); a cycle no job needs is not added.
Cycles a dispatch or a report protects are neither taken off nor built through.
Select the whole run before changing its length; Run cycles counts the selected cycles.

Notes

A note belongs to an order's or a stock rule's job, a mold or a machine-day, never one cycle: it would stay behind when its run moves.
A note changes no light and blocks nothing; the app does not interpret its text.
Notes are outside Undo and Redo. They save when the field loses focus; text still being typed when the window closes, or when Escape clears the selection, is not saved.
Notes do not go into the production log. The day's note stays with the day. The machine-day sheet prints the day's and the molds' notes, not the jobs'.
A named version holds the plan only. Opening it keeps the notes currently in use.
Renaming a machine in Factory inputs leaves its days' notes behind. An import starts a new plan with no notes.
One note per job, mold or machine-day, up to 2,000 characters; no history, author or time. See Notes that stay.

Files and support reports

A plan saved by the earlier 0.3.1 trial, or one saved before this version that holds a dispatch, is not opened by this version. Its autosave may be set aside with a message calling it damaged. Keep the older app and saved file together if you need that plan; use the current sample for this version.
A support recording is replayed with the version that recorded it. Send the report with that version number; do not use another version to reproduce it.
A canceled take that first introduced a new shape cannot be replayed reliably from its report. Include a screenshot and describe the canceled action when contacting support.
Changing shared settings while RotoScheduler is running can give a report that replays with the settings from the session's start. Save settings in RotoSpider, then restart RotoScheduler before recording the next attempt.
Taking from a folder with no workbook fails. With recording on, it also leaves that session's report incomplete. Restore the supplied workbook and shape files, restart RotoScheduler, then try again.

Comments and questions

The app's rules are our reading of the physics; where your plant knows better, the app changes.

Email a suggestion or comment

Start here

Read the board

Jobs and the factory

Edit the plan

Documents and files

Reference