RotoScheduler manual › Documents and files

Save and reopen a plan

Describes RotoScheduler 0.3.3 · checked 2026-10-19 D5

Click Save and choose a filename and folder. A schedule document is a .json file. It keeps the factory inputs, orders, plan, saved moves, notes, board view, production log and clock setting.

To try reopening, set September 7 to Day with RM-4 unfolded, save the file, then click Open and select it again. The plan returns with the saved view. The app works on one schedule document at a time.

What each kind of file keeps

Use Save for a portable copy of one plan. In the browser, the working document and its versions stay in the site's storage: clearing site data removes them, and downloaded files stay where the browser saved them.

The browser opens stored plans that do not need automatic planning. A desktop document that requires Generate may be refused by the demo; keep such a plan in the desktop application.

Opening an older file for the plant already in use keeps the live production log. The file is first opened with its own log and saved moves to recover its board. That board is then checked against the live dispatches: protected cycles and mold removals come from their dispatch, and unprotected loads that no longer fit come off and are listed. The accepted board starts a new Undo history. A file for another plant replaces the current plant and its log. A named version restores only the plan against today's facts; see Keep a named version.

Not supported

• Two RotoSchedulers open on one data folder at once: two versions side by side, or two computers syncing the folder. The folder holds one working plan, saved whole at every change, a zoom included, so once one window changes it the other refuses every change with "This plan was changed by another RotoScheduler on this data folder. Close this window and open it again." It can still save a named version or a file, and close; after a refused Factory inputs, file or version open, Dispatch or Take back, Versions and Save stay disabled until Restore saved plan is clicked. Nothing is merged, and a folder synced between computers can still lose a change that arrives during a save.
• A plan or version written by a version of the app with another file schema: such a plan opens on the damaged-autosave panel, whose starter replaces it (schedule/quarantine-current.json keeps the last copy); versions saved by 0.3.1 or 0.3.2 are not listed, their files remain. Save to a file before switching versions.
• Files under schedule edited or copied by hand: one damaged version file stops Versions for every plan. A crash during a save can leave a .tmp file there, which nothing reads.
• Two versions, or RotoSpider and RotoScheduler, open on one account's data folder, or two computers syncing it: each Apply in Settings writes back the settings it loaded, so the last Apply wins.
• Dispatch lines brought back from another computer are not merged into the live log. Returning to a replaced plant from an older file and recovering its identity from damaged storage are not supported.
• The compact document is limited to 8 MiB, and an opened file to 64 MiB. There is no archive of old production-log lines yet. Reopening a plan solves its mold layouts again from today's facts; it does not preserve the previously accepted layout.