Scheduled scan floods logs with `SqliteError: ON CONFLICT clause does not match any PRIMARY KEY or UNIQUE constraint` on `open-epub`

After pulling the latest update, every scheduled scan dumps long SQLite errors for many books: WARN: [SCAN:scheduled] [open-epub] Step open-epub failed for book <title> followed by SqliteError: ON CONFLICT clause does not match any PRIMARY KEY or UNIQUE constraint and Unhandled error scanning /path/to/library/....epub (ebook). Around 18 books are affected and the log is truncated, so possibly more. Is this safe to ignore?

Resolution: The error comes from the EPUB 2 → EPUB 3 conversion-and-backup path: Storyteller now requires books entering the library to be EPUB 3, and the backup-then-convert flow hit a bad upsert that aborts the scan step. It is non-destructive to the source file, but left alone it can keep generating extra backup copies in the book's folder, so check the affected books' directories for accumulated backups. Two options: upgrade — the fix shipped in the release cut right after this was reported, after which those books import and back up correctly with the default behavior; or, if you can't upgrade yet, change the EPUB 2 handling setting to "convert in place" (rewrites the source file, no backup copy) or "skip epub 2 files" (ignores them entirely, which is effectively what is already happening). Note that Storyteller's own EPUB 2 backup files left behind by earlier conversions are picked up by the scan too, so they can be the source of the errors even if you believe your library is fully EPUB 3.