Script Studio

Reconcile + No Snapshot: post-import reconciliation and restore caveat

4 min read

After import, you may find content conflicting with the existing script book (e.g. duplicate scenes) — Slima's "Reconcile" tool helps you resolve them. "No snapshot" is a special state: no version snapshot before import.

Slima Script Studio Plan view as a visual reference; Reconcile is available after large imports or via Series settings

What Reconcile is

After bulk-importing multiple Episodes, you might find:

  • Some Episodes duplicate existing ones (you chose "create new", so now two copies)
  • Character names inconsistent across old / new (e.g. "Wang Xiaoming" / "王小明" / "Mr. Wang")
  • Locations repeating under different names

Reconcile = compare old vs new content; merge or pick which to keep.

Triggering Reconcile

After import, usually:

  • Notification: "N entities have conflicts — reconcile now?"
  • Or manually from Series settings → "Reconcile" entry

Reconcile UI

Typically organised by category:

Duplicate Episodes

Potential duplicate:
- E01: original "E01: The Departure" vs newly-imported "E01: 起點"
  → [keep both] / [merge] / [delete original] / [delete newly-imported]

Character conflicts

Character name conflict:
- 王小明 (original) ≈ Wang Xiaoming (new) ≈ Mr. Wang (new)
  → Unify all three as which name? [王小明] [Wang Xiaoming] [Mr. Wang]

Location conflicts

Location conflict:
- Lighthouse Cottage (original) ≈ Lighthouse Keeper's Cottage (new)
  → Unify as which?

After your choice → Slima updates all references in one pass.

"No snapshot" state

If something interrupted during import or the dataset was huge, Slima may fail to capture a full pre-import snapshot — the book is flagged as "No snapshot" state.

Meaning:

  • Content imported successfully
  • No full pre-import version to restore (partial auto-version fragments may exist)
  • Pre-import history may be incomplete

If you hit "No snapshot"

To restore options:

  • Check version history for any partial auto-version recoverable
  • See Bulk-import from .slima backup (if you exported a backup earlier)
  • Accept the new state and keep writing

Prevention

  • Export a .slima backup before large imports
  • Import in batches (avoid one massive import)

Reconcile auto-detection limits

Slima uses fuzzy matching (e.g. Levenshtein distance) to detect duplicates — but never auto-merges, always asks your confirmation.

If you imported in bulk without reconciling, old and new data coexist (duplicates allowed). Trigger Reconcile from Series settings any time afterwards.

Related

Was this helpful?