Keep safe · Answers

Troubleshooting and glossary

Most blocking messages are safeguards, not dead ends. Preserve the authoritative copy, restore the expected storage state, and retry from the action that reported the problem.

Storage problems

Offline

Reconnect or remount the configured disk/share. Confirm its status becomes Online before using file actions. Episode metadata remains searchable while the archive is disconnected.

Read only

The root can be inspected but cannot accept imports or transfers. Check disk permissions, filesystem state, mount options, and free space outside the app, then let the monitor refresh.

Wrong volume

A disk or share exists at the expected path but does not match the remembered volume identity. Do not relink it casually. Eject the unexpected volume and reconnect the configured one.

Folder missing

The storage root is reachable, but the episode’s recorded relative folder is absent. Reconnect the correct root or restore the folder and its matching manifest. Changing a root cannot manufacture or move the missing folder.

Save and catalogue problems

Changes may not be saved

Treat the global banner as blocking. Choose Retry save, then Reveal library if it persists. Preserve the catalogue, newly written media, and current working information before quitting.

Catalogue from a newer version

An older app build opens a newer unsupported schema read-only rather than overwriting it. Reopen the library with the newer app build that created it.

Unreadable catalogue

The app requires a byte-verified rescue copy before using fallback data. Preserve library.json, any library.corrupt-*.json copy, and library-backups before attempting manual repair.

Import problems

Import needs attention

Read the batch counts. Some files may have succeeded while others failed or were cancelled. Originals remain unchanged. Reveal the destination and inspect verified results rather than restarting the whole batch blindly.

Verified uncatalogued file

The byte copy completed, but the catalogue save failed. Reveal and preserve the file, resolve the global save problem, then decide whether to catalogue or re-import it. Do not discard it merely because it is absent from the library.

Cannot import to an archived episode

Restore the episode to Primary storage first. Imports also wait for any active archive/restore or pending cleanup to finish.

Script and recovery problems

Script changed on disk

The save is being refused to prevent silent overwrite. Compare the external file with the in-app/recovery draft, merge intentionally, and reload only when the disk version should win.

Draft belongs to an old script path

The episode’s linked path changed after the draft was made. Do not automatically restore it over the new target. Preserve and compare the draft, then move useful text manually.

Recovery draft is unreadable

Preserve the file in the Script Recovery Drafts folder before replacing or removing it. Use a text or recovery tool on a copy.

Publishing readiness problems

Open the failed row; its detail tells you whether storage, a real file, render status, required checklist, description, or planned release is missing. A path string, Ready status, or Today summary cannot substitute for the full seven-item assessment.

Archive and cleanup problems

Move or relink the script, linked media, thumbnail, final export, and editing project inside the episode folder. Archive is blocked while those episode-owned links point elsewhere.

Retry cleanup

The verified destination is active, but the old source remains. Reconnect both roots and use Retry cleanup; the app re-verifies before removal. Do not manually choose which copy to delete.

Glossary

TermMeaning
ChannelA publishing identity and the top-level scope for all visible production data.
SeriesA repeatable episode format with folders, copy-template files, defaults, checklist, and optional shared assets.
SingleA standalone episode using the channel’s Singles template.
EpisodeOne video’s production record, folder, workflow, and publishing packet.
Planning taskCreator-owned work with category, status, priority, dates, notes, and optional links.
Generated milestoneA recording, release, upload, or idea target derived from the source record that owns it.
Planned releaseThe intended date and time of publication.
Published externallyConfirmation that publication actually happened outside the app.
Primary storageWritable storage for active work, reusable media, templates, and assets.
Archive storageOptional storage for completed episode folders.
Copy templateFiles physically copied from a Series or Singles template folder into a new episode.
Shared assetA channel-wide Assets record linked to a series without copying the file into each episode.
Project FilesThe legitimate episode folder for editing-tool project files. The app otherwise uses “Episode,” not legacy “Project,” terminology.