Skip to the article
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 local-library problems

### Changes may not be saved

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

### Catalogue from a newer version

An older app build leaves a newer SQLite storage or content schema untouched rather than overwriting it. Reopen the library with the newer app build that created it.

### Unreadable catalogue

The app requires byte-verified rescue copies before using fallback data. Preserve `library.sqlite`, its existing `-wal`/`-shm` sidecars, every `library.corrupt-*` copy, and `library-backups` before attempting manual repair. Never delete one SQLite family member independently.

## 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.

## Editing-project media problems

### Clips became offline after an app launch

Check the episode’s `Footage` folder in Finder. A recording discovered in place becomes managed media, and the app can give it a portable filename on a later launch or library reload. For example, `After2AM 2026-08-03 10.59.10.mov` becomes `After2AM 2026-08-03 10 59 10.mov`. DaVinci Resolve or another editor may still be looking for the old filename.

Preserve the editing project, reveal the actual managed file, and relink the offline clip to it. For future recordings, have the recorder create portable names without extra punctuation, or restart After2AM Studio once after discovery and verify the final names before bringing the clips into the editor.

## Document and script recovery problems

### A recovered note conflicts with its committed version

Recovery is not an automatic commit. Compare the recovered draft with the last saved note, then explicitly resume or discard it. Studio will not choose a winner when both versions changed.

### 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

### Episode links cannot travel

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

Term | Meaning
--- | ---
Channel | A publishing identity and the top-level scope for all visible production data.
Series | A repeatable episode format with folders, copy-template files, defaults, checklist, and optional shared assets.
Single | A standalone episode using the channel’s Singles template.
Episode | One video’s production record, folder, workflow, and publishing packet.
Planning task | Creator-owned work with category, status, priority, dates, notes, and optional links.
Generated milestone | A recording, release, upload, or idea target derived from the source record that owns it.
Planned release | The intended date and time of publication.
Published externally | Confirmation that publication actually happened outside the app.
Primary storage | Writable storage for active work, reusable media, templates, and assets.
Archive storage | Optional storage for completed episode folders.
Copy template | Files physically copied from a Series or Singles template folder into a new episode.
Shared asset | A channel-wide Assets record linked to a series without copying the file into each episode.
Project Files | The legitimate episode folder for editing-tool project files. The app otherwise uses “Episode,” not legacy “Project,” terminology.